From: Andreas Dilger <adilger@sun.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: "Ted Ts'o" <tytso@thunk.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: large file system & high object count testing
Date: Mon, 31 Aug 2009 17:16:44 -0600 [thread overview]
Message-ID: <20090831231644.GK4197@webber.adilger.int> (raw)
In-Reply-To: <4A9C3A30.5060401@redhat.com>
On Aug 31, 2009 17:01 -0400, Ric Wheeler wrote:
> On 08/31/2009 04:19 PM, Andreas Dilger wrote:
>> Ouch, 4h is a long time, but hopefully not many people have to reformat
>> their 120TB filesystem on a regular basis.
>
> Seems that it should not take longer than fsck in any case? Might be
> interesting to use bkltrace/seekwatcher to see if it is thrashing these
> big, slow drives around...
Well, e2fsck + gdt_csum can skip reading large parts of an empty
filesystem, while ironically mke2fs is required to initialize it all.
>>> [root@megadeth e2fsck]# time ./e2fsck -f -tt /dev/vg_wdc_disks/lv_wdc_disks
>>> e2fsck 1.41.8 (20-Jul-2009)
>>> Pass 1: Checking inodes, blocks, and sizes
>>> Pass 1: Memory used: 1280k/18014398508273796k (1130k/151k), time:
>>> 4630.05/780.40/3580.01
>>
>> Sigh, we need better memory accounting in e2fsck. Rather than depending
>> on the VM/glibc to track that for us, how hard would it be to just add
>> a counter into e2fsck_{get,free,resize}_mem() to track this?
>
> That second number looks like a bug, not a real memory number. The
> largest memory allocation I saw while it ran with top was around 6-7GB
> iirc.
Sure, it is a 32-bit overflow (which is the most this API can provide),
which is why we should fix it.
>> Hmm, is e2fsck computing the 64-byte group descriptor checksum differently
>> than the kernel? Can we dump the group descriptors before and after the
>> e2fsck run to see whether they have been modified without any messages to
>> the console?
>
> I tried to verify that by redoing a shorter run with fs_mark,
> unmount/remount (no fsck in the middle).
>
> That file system remounted with no corrupted group descriptors.
>
> Running fsck on it & remounting reproduces the error (although, again, no
> fixes reported during the run).
>
> Running fsck on it after the first corruption did indeed fix it & I could remount.
>
> Do you have a specific debugfs/other command I should use to poke at it with?
Getting dumps of the corrupted group descriptors before/after corruption,
to see what the values are, per my other email.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
prev parent reply other threads:[~2009-08-31 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 16:34 large file system & high object count testing Ric Wheeler
2009-08-31 17:02 ` Ric Wheeler
2009-08-31 20:56 ` Andreas Dilger
2009-08-31 21:02 ` Ric Wheeler
2009-08-31 21:25 ` Justin Maggard
2009-08-31 22:20 ` Ric Wheeler
2009-08-31 23:13 ` Andreas Dilger
2009-08-31 23:37 ` Justin Maggard
2009-09-02 9:15 ` Andreas Dilger
2009-08-31 20:19 ` Andreas Dilger
2009-08-31 21:01 ` Ric Wheeler
2009-08-31 23:16 ` Andreas Dilger [this message]
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=20090831231644.GK4197@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=tytso@thunk.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;
as well as URLs for NNTP newsgroup(s).