| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090718181921.GA8990@infradead.org> Date: Sat, 18 Jul 2009 14:19:22 -0400 From: Christoph Hellwig <hch@...radead.org> To: Andi Kleen <andi@...stfloor.org> Cc: Theodore Tso <tytso@....edu>, Andreas Dilger <adilger@....com>, device-mapper development <dm-devel@...hat.com>, Neil Brown <neilb@...e.de>, linux-fsdevel@...r.kernel.org, linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: How to handle >16TB devices on 32 bit hosts ?? On Sat, Jul 18, 2009 at 04:21:56PM +0200, Andi Kleen wrote: > > We don't have to rewrite fsck; most of the framework for supporting an > > run-length-conding for compressed bitmaps is already in patches that > > add > 32-bit block numbers to e2fsprogs; we've just been more focused > > on getting 64-bit block numbers support merged than implementing > > compressed bitmaps, but it's only one file that would need to be > > added, and we might be able to steal the compressed bitmap support > > from xfsprogs --- which does this already. > > There are regular reports of xfs_repair failing on 32bit, > even on volumes far smaller than 16TB. We have a set of patches pending to reduce memory use in xfs_repair dramaticly, replacing bitmaps for tracking used blocks with extent structures stored in btrees. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists