linux-kernel - Re: How to handle >16TB devices on 32 bit hosts ??

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090718134946.GA25546@mit.edu>
Date:	Sat, 18 Jul 2009 09:49:46 -0400
From:	Theodore Tso <tytso@....edu>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	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 09:48:11AM +0200, Andi Kleen wrote:
> 
> > Also, for filesystems like btrfs or ZFS the checking can be done
> > online and incrementally without storing a full representation of
> > the state in memory.
> 
> You could, but I suspect it would be cheaper to just use a
> 64bit system than to rewrite fsck. 64bit is available
> for a lot of embedded setups these days too.

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.

						- Ted
--
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/