On Tue, Mar 17, 2015 at 4:20 PM, Linda Walsh
Chris Murphy wrote:
Ishtar:/sys/devices/pci0000:00/../sda/queue> pwd
/sys/devices/pci0000:00/0000:00:09.0/0000:07:00.0/host0/target0:2:0/0:2:0:0/block/sda/queue Ishtar:/sys/devices/pci0000:00/../sda/queue> cat logical_block_size 512 Ishtar:/sys/devices/pci0000:00/../sda/queue> cat physical_block_size 4096 Ishtar:/sys/devices/pci0000:00/../sda/queue>
This is clearly a 512e drive, not 512n.
=== Ok.. mea culpa -- when I read the specs, the native drive didn't have a suffix... but i'm sure that highlighted the difference too well. Though, I'm not sure I agree with your adjective "clearly"... *ahem*...
Yeah I can definitely appreciate that. The terms are non-obvious. Presumably 512n as a term only came about after 512e, despite being first. And it's also true that kernel reporting logical/physical is only consistent in a direct attached (no enclosure) context. Thus far I've seen enclosures misreport 512e drives as logical_block_size 512 physical_block_size 512 and also logical_block_size 4096 physical_block_size 4096 I haven't yet seen an encosure either correctly pass through, or obscate a 512n drive such that logical_block_size 512 physical_block_size 4096 Which is the only totally unclear way I arrived at clearly it's 512e. Passthrough would be good, but obfuscating a 512n drive as having 4096 byte physical sectors would be sabotage.
That's what I get for not rechecking current terminology before posting.
:-( <---*bang*
Oh no, wait for the base 2 / IEC / kibi,mebi,gibi vs base 10 / SI / kilo,mega,giga thread. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org