Re: thin provisioned LUN support & file system allocation policy

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

 



David Woodhouse wrote:
On Fri, 7 Nov 2008, jim owens wrote:

Ric Wheeler wrote:

The type of allocation that would help most is something that tries to keep the lower block ranges "hot" for allocation, second best policy would simply keep the allocated blocks in each block group hot and re-allocate them.

This block reuse policy ignores the issue of wear leveling...
as in most design things, trading one problem for another.

For SSDs we're being told not to worry our pretty little heads about wear levelling. That gets done for us, with varying degrees of competence, within the black box. All we can do to improve that is pray... and maybe sacrifice the occasional goat.


I'm talking DISK wear not SSD.  The array vendors who are causing
this problem are doing petabyte san devices, not SSDs.

Rewriting the same sectors causes more bad block remaps
until the drive eventually runs out of remap space.



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

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux