From: Justin Maggard <jmaggard10@gmail.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Ric Wheeler <rwheeler@redhat.com>,
linux-ext4@vger.kernel.org, "Ted Ts'o" <tytso@thunk.org>
Subject: Re: large file system & high object count testing
Date: Mon, 31 Aug 2009 16:37:16 -0700 [thread overview]
Message-ID: <150c16850908311637t18683386j66bcebd06fe05e9b@mail.gmail.com> (raw)
In-Reply-To: <20090831231331.GJ4197@webber.adilger.int>
On Mon, Aug 31, 2009 at 4:13 PM, Andreas Dilger<adilger@sun.com> wrote:
> Justin, could you please replicate this corruption, collecting some
> additional information before & after. My recollection is that the
> corruption appears in the first few groups, so 64kB should be plenty
> to capture the group descriptor tables (where the checksum is kept).
>
> - mke2fs
> - dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-new.gz
> - mkdir ...
> - sync
> - dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-mkdir.gz
> - umount
> - dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-umount.gz
> - e2fsck
> - dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-e2fsck.gz
>
No problem. I just sent you an email with those four attached. If
anyone would like me to upload them somewhere else, just let me know.
-Justin
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-31 23:43 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 [this message]
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
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=150c16850908311637t18683386j66bcebd06fe05e9b@mail.gmail.com \
--to=jmaggard10@gmail.com \
--cc=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).