From: Justin Maggard <jmaggard10@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Valerie Aurora <vaurora@redhat.com>,
Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org, Nick Dokos <nicholas.dokos@hp.com>,
Julia Lawall <julia@diku.dk>
Subject: Re: >16TB issues
Date: Fri, 28 Aug 2009 13:27:26 -0700 [thread overview]
Message-ID: <150c16850908281327g77bd0c5cmda53310d68742263@mail.gmail.com> (raw)
In-Reply-To: <20090828124013.GB16732@mit.edu>
On Fri, Aug 28, 2009 at 5:40 AM, Theodore Tso<tytso@mit.edu> wrote:
> Um, that's interesting. What happens if run fsck.ext4 twice? i.e:
>
Here's what happens with an immediate fsck after the first one.
Again, if I don't create the directories, there are no errors.
# fsck.ext4 -C0 -fy /dev/md0
e2fsck 1.41.8 (20-Jul-2009)
One or more block group descriptor checksums are invalid. Fix? yes
Group descriptor 0 checksum is invalid. FIXED.
Group descriptor 1 checksum is invalid. FIXED.
Group descriptor 2 checksum is invalid. FIXED.
Group descriptor 3 checksum is invalid. FIXED.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/md0: 16/365234176 files (0.0% non-contiguous), 23315701/5843746816 blocks
# echo $?
0
# fsck.ext4 -C0 -fy /dev/md0
e2fsck 1.41.8 (20-Jul-2009)
One or more block group descriptor checksums are invalid. Fix? yes
Group descriptor 1 checksum is invalid. FIXED.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/md0: 16/365234176 files (0.0% non-contiguous), 23315701/5843746816 blocks
# echo $?
0
-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-28 20:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 22:23 >16TB issues Justin Maggard
2009-07-03 14:38 ` Andreas Dilger
2009-07-16 18:04 ` Justin Maggard
2009-07-16 18:59 ` Valerie Aurora
2009-07-21 16:10 ` Andreas Dilger
2009-07-21 18:52 ` Justin Maggard
2009-07-21 18:57 ` Eric Sandeen
2009-07-21 19:21 ` Andreas Dilger
2009-07-22 22:27 ` Justin Maggard
2009-07-27 22:03 ` Valerie Aurora
2009-07-30 22:23 ` Valerie Aurora
2009-08-01 1:24 ` Justin Maggard
2009-08-03 17:20 ` Valerie Aurora
2009-08-11 21:39 ` Valerie Aurora
2009-08-11 22:05 ` Theodore Tso
2009-08-12 1:25 ` Valerie Aurora
2009-08-12 2:04 ` Theodore Tso
2009-08-12 17:59 ` Valerie Aurora
2009-08-28 2:30 ` Justin Maggard
2009-08-28 12:40 ` Theodore Tso
2009-08-28 20:27 ` Justin Maggard [this message]
2009-08-12 4:21 ` Eric Sandeen
2009-08-12 5:35 ` Justin Maggard
2009-08-12 14:12 ` Eric Sandeen
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=150c16850908281327g77bd0c5cmda53310d68742263@mail.gmail.com \
--to=jmaggard10@gmail.com \
--cc=adilger@sun.com \
--cc=julia@diku.dk \
--cc=linux-ext4@vger.kernel.org \
--cc=nicholas.dokos@hp.com \
--cc=tytso@mit.edu \
--cc=vaurora@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).