From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: E2fsprogs master branch now has all 64-bit patch applied
Date: Mon, 14 Jun 2010 09:41:30 -0500 [thread overview]
Message-ID: <4C163F9A.2080908@redhat.com> (raw)
In-Reply-To: <E1OO9sy-0006P1-Nr@closure.thunk.org>
Theodore Ts'o wrote:
...
> What are things that are still left to be done before we 64-bit support
> is completely supported? Just a few things:
>
> * Currently the badblocks list mechanism only supports 32-bit blocks.
> This may be OK, since running "badblocks" on a really large disk is
> probably a fool's errand. But how we handle this is an open question;
> should we just refuse "mke2fs -c" or "e2fsck -c" for really big file
> systems? Should we deprecate the badblocks inode altogether?
>
> * The online resizing code, which relies on using a resize inode and
> indirect blocks, will not scale to 64-bit filesystems. We have the
> beginnings of support for the "meta_bg" style of resizing, which is
> supported by the kernel and the e2fsprogs code --- but it hasn't been
> implemented in the kernel yet. We need to add that.
* Lazy inode table initialization so that large fs mkfs time is acceptable.
-Eric
next prev parent reply other threads:[~2010-06-14 14:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 13:39 E2fsprogs master branch now has all 64-bit patch applied Theodore Ts'o
2010-06-14 14:41 ` Eric Sandeen [this message]
2010-06-14 14:46 ` Ric Wheeler
2010-06-14 20:15 ` Eric Sandeen
2010-06-14 20:26 ` Valerie Aurora
-- strict thread matches above, loose matches on Subject: below --
2010-06-21 13:59 陳炫廷
2010-06-21 17:02 Andreas Dilger
[not found] <AANLkTilD3D2QOXi1b7oXT2uFBx_vuO803HOX4JJXfWG0@mail.gmail.com>
2010-06-21 17:05 ` tytso
2010-06-22 9:15 ` Hsuan-Ting
2010-06-22 16:17 ` Andreas Dilger
2010-06-23 8:42 ` Hsuan-Ting
2010-06-23 11:00 ` Hsuan-Ting
2010-06-25 10:33 ` Hsuan-Ting
2010-06-25 18:23 ` Andreas Dilger
2010-06-29 13:41 ` Hsuan-Ting
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=4C163F9A.2080908@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--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).