Re: [PATCH, RFC] mke2fs: get device topology values from blkid

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/20/2009 01:46 PM, Martin K. Petersen wrote:
"Andreas" == Andreas Dilger<adilger@xxxxxxx>  writes:
Andreas>  Yes, there is more chance that writing sector 7 (due to 4k
Andreas>  sector r-m-w) will cause collateral damage, but the truth even
Andreas>  today is that disks are not going to fail a single 512-byte
Andreas>  sector at one time, but more likely 64kB (or whatever the
Andreas>  remapping unit size is), so this isn't really introducing a new
Andreas>  failure mode.

I keep hearing this disk drive "internal block size" of 32KB or 64KB
being mentioned.  And yet none of the drive firmware engineers I talk to
on a regular basis have ever heard of such a thing...

I have not heard of drives with that kind of internal block size for single drives.

What is common is that reads (often) are often done in much larger chunks like this (basically, if you are reading, it normally makes sense to read a whole track from the platter :-)

Array vendors definitely do have larger internal block sizes.

ric


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux