From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
device-mapper development <dm-devel@redhat.com>,
Neil Brown <neilb@suse.de>,
linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: How to handle >16TB devices on 32 bit hosts ??
Date: Sat, 18 Jul 2009 14:19:22 -0400 [thread overview]
Message-ID: <20090718181921.GA8990@infradead.org> (raw)
In-Reply-To: <20090718142156.GC2682@basil.fritz.box>
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.
next prev parent reply other threads:[~2009-07-18 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 0:08 How to handle >16TB devices on 32 bit hosts ?? Neil Brown
2009-07-18 4:31 ` Andreas Dilger
2009-07-18 6:16 ` Andi Kleen
2009-07-18 6:52 ` Andreas Dilger
2009-07-18 7:48 ` Andi Kleen
2009-07-18 13:49 ` Theodore Tso
2009-07-18 14:21 ` Andi Kleen
2009-07-18 14:32 ` Andreas Dilger
2009-07-18 18:19 ` Christoph Hellwig [this message]
2009-07-29 15:07 ` Pavel Machek
2009-07-19 3:44 ` Tapani Tarvainen
2009-07-18 6:09 ` Andi Kleen
2009-07-22 6:59 ` Andrew Morton
2009-07-22 18:32 ` Andreas Dilger
2009-07-22 18:51 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090718181921.GA8990@infradead.org \
--to=hch@infradead.org \
--cc=adilger@sun.com \
--cc=andi@firstfloor.org \
--cc=dm-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).