From: Andreas Dilger <adilger@sun.com>
To: Ron Johnson <ron.l.johnson@cox.net>
Cc: Linux-Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: EXT4-fs: group descriptors corrupted!
Date: Wed, 25 Feb 2009 17:05:41 -0700 [thread overview]
Message-ID: <20090226000541.GC3199@webber.adilger.int> (raw)
In-Reply-To: <49A5D74D.9030309@cox.net>
On Feb 25, 2009 17:42 -0600, Ron Johnson wrote:
> On 02/25/2009 05:18 PM, Theodore Tso wrote:
>> Now let's take a look at your dumpe2fs output. In your case, we see
>> the following:
>>
>> Filesystem created: Thu Jan 22 19:33:20 2009
>> Last mount time: Fri Jan 23 16:23:58 2009
>> Last write time: Sun Feb 22 02:31:02 2009
>> Mount count: 1
>> Maximum mount count: 24
>> Last checked: Fri Jan 23 16:19:49 2009
>> Check interval: 15552000 (6 months)
>> Next check after: Wed Jul 22 17:19:49 2009
>>
>> and it's the same on both the primary and backup (dumpe2fs -o
>> superblock=32768). The question is how the heck did *that* happen?
>> As I mentioned, the kernel doesn't even have code to touch the backup
>> superblock.
Except online resizing? It HAS to update the backup superblocks,
otherwise if the primary gets corrupted the backup will not have
the right total blocks count and anything beyond the old blocks
count might be lost...
>> Does that the "last write" timestamp suggest anything to you? What
>> was happening on the system at or around Sun Feb 22 02:31:02 2009?
>> Maybe if we can localize this down to what userspace program caused
>> the problem, it'll be a hint.
>
> That's about 10 hours before I rebooted the machine, middle of a
> Saturday night...
Please take time zones into account also.
> I performed a rather large apt-get upgrade at around 01:30, but that
> would have only touched /, not my "big data" directory. ~/Documents is
> symlinked into /data/big/Documents, so I might have been editing an OOo
> document, or copying a YouTube file to it, but nothing pops into mind.
This might have happened AFTER your reboot, by e2fsck or similar?
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-02-26 0:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 20:39 EXT4-fs: group descriptors corrupted! Ron Johnson
2009-02-25 21:30 ` Theodore Tso
2009-02-25 21:47 ` Ron Johnson
2009-02-25 23:18 ` Theodore Tso
2009-02-25 23:41 ` Greg Freemyer
2009-02-25 23:42 ` Ron Johnson
2009-02-26 0:05 ` Andreas Dilger [this message]
2009-02-26 0:23 ` Ron Johnson
-- strict thread matches above, loose matches on Subject: below --
2009-03-07 6:55 Christian
2009-03-09 16:13 ` Christian
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=20090226000541.GC3199@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ron.l.johnson@cox.net \
/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).