public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-ext4@vger.kernel.org
Subject: Re: ext4 64bit (disk >16TB) question
Date: Tue, 15 Jul 2008 14:12:19 -0600	[thread overview]
Message-ID: <20080715195116.GL6239@webber.adilger.int> (raw)
In-Reply-To: <20080715132734.68c64000@ichigo>

On Jul 15, 2008  13:27 -0500, Jose R. Santos wrote:
> On Mon, 14 Jul 2008 21:50:56 +0200
> Goswin von Brederlow <goswin-v-b@web.de> wrote:
> > we are using lustre on a cluster of servers and raid boxes. Currently
> > lustre is based on the ext3 code and has a limit of 8TiB for each
> > filesystem. For us that results on having to split a servers storage
> > into up to 4 chunks and run one fs on each which I would rather avoid.
> > The solution for this would be to rebase the lustre patches to use
> > ext4 instead, which should also reduce the patch set considerably.
> > Lustre already patches a lot of ext4 features into the ext3 base.
> > 
> > 
> > But before I start rebasing lustre I though I would first test out
> > plain ext4 so I know any bugs I find will be from my rebasing and not
> > already existing in ext4 itself. And there I run into a big problem:
> > Current e2fsprogs (1.41) seem to be totaly unable to handle the ext4 64BIT
> > feature, i.e. filesystems larger than 16TiB. The mkfs.ext4 always
> > stops saying the disk exceeds the 32bit block count. And looking at
> > the code I see a lot of blk_t (instead of blk64_t) and unsigned long
> > (instead of unsigned long long [or even better blk64_t]) usage.
> > 
> > I found ext4 64bit patches for e2fsprogs 1.39 that fix at least
> > mkfs. Does anyone know if there is an updated patch set for 1.41
> > anywhere? And when will that be added to e2fsprogs upstream?
> 
> I've recently submitted a set of patches that covers most of the API
> changes needed to support >16TB file systems (missing Ted bitmap
> support of course).  Once the bitmap support is included, it _SHOULD_
> be relatively painless to add mke2fs support with this series of patches.

Jose,
while waiting for the "efficient bitmap" support, how hard would it be
to implement "inefficient bitmaps" that just malloc some GB of memory
if needed?  This would at least allow people with huge devices to test
mke2fs/ext4/e2fsck in the meantime.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  reply	other threads:[~2008-07-15 20:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 19:50 ext4 64bit (disk >16TB) question Goswin von Brederlow
2008-07-14 23:46 ` Theodore Tso
2008-07-15  5:42   ` Goswin von Brederlow
2008-07-15 12:36     ` Theodore Tso
2008-07-15 17:00       ` Goswin von Brederlow
2008-07-15 17:19         ` Theodore Tso
2008-07-15 13:16     ` Ric Wheeler
2008-07-15 14:01       ` Bernd Schubert
2008-07-15 14:08         ` Ric Wheeler
2008-07-15 16:13           ` Goswin von Brederlow
2008-07-15 18:27 ` Jose R. Santos
2008-07-15 20:12   ` Andreas Dilger [this message]
2008-07-15 20:15     ` Ric Wheeler
2008-07-15 21:03       ` Goswin von Brederlow
2008-07-15 21:20     ` Jose R. Santos
2008-07-16 10:10       ` Goswin von Brederlow

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=20080715195116.GL6239@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=goswin-v-b@web.de \
    --cc=jrs@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    /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