From: Andreas Dilger <adilger@sun.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] debugfs: open with EXT2_FLAG_64BITS
Date: Sat, 12 Sep 2009 22:29:19 +0200 [thread overview]
Message-ID: <20090912202919.GY9372@webber.adilger.int> (raw)
In-Reply-To: <4AAA6A44.90902@redhat.com>
On Sep 11, 2009 10:18 -0500, Eric Sandeen wrote:
> Pointing debugfs from the pu branch at a large filesystem is
> still failing with:
>
> Filesystem too large to use legacy bitmaps while reading block bitmap
>
> We need to open with EXT2_FLAG_64BITS; I'm not sure if this
> should be a switch based on the size of the fs or not?
The one thing that is already VERY painful is the time it takes for
debugfs to read the bitmaps from disk at startup. Running with
"-c" allows that step to be skipped, but tha means it isn't possible
to modify the filesystem at all.
The time for 8TB filesystems is already in the multi-minute range, so
I can't imagine how long it will take on huge filesystems. The only
saving grace might be flex_bg avoiding seeks between every pair of
bitmaps.
Has any attention been given to the ext2fs_load_bitmaps() function for
flex_bg filesystems? This would need to be tuned to read groups_per_flex
block bitmaps first, then groups_per_flex inode bitmaps before skipping
to the next flex group. Otherwise we may still be reading each pair of
block+inode bitmaps at a time, and only by virtue of disk track caching
are we avoiding a seek between each one (which would eventually break
down once the groups_per_flex exceeds the track cache size).
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-09-12 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 15:18 [PATCH] debugfs: open with EXT2_FLAG_64BITS Eric Sandeen
2009-09-12 20:29 ` Andreas Dilger [this message]
2009-10-08 20:17 ` Eric Sandeen
2009-10-26 5:15 ` Theodore Tso
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=20090912202919.GY9372@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).