Re: thin provisioned LUN support & file system allocation policy

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

 



Martin K. Petersen wrote:
"Ted" == Theodore Tso <tytso@xxxxxxx> writes:

Ted> How much of a disk wear factor is there with modern disk drives?
Ted> The heads aren't touching the disk, and we have plenty of sectors
Ted> which are constantly getting rewritten with traditional
Ted> filesystems, with no ill effects as far as I know.

Modern disk firmware maintains a list of write hot spots and will
regularly rewrite adjacent sectors to prevent bleed.

This is my understanding (based on looking at lots of disks from my EMC days). Again, this is not an issue for a Symm/Hitachi/Shark class array since they all abstract away this kind of hot spotting.

Where it is an issue with local drives is when you constantly (like every 20ms) try to update the same sector and that triggers the kind of adjacent track erasure issues you mention here. Disk block allocation policies that reuse blocks will update the same sectors are orders of magnitude less than this (and much less than we rewrite block allocation bitmaps, etc).

ric

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux