From: Phillip Susi <phill@thesusis.net>
To: Luigi Fabio <luigi.fabio@gmail.com>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: RAID5 failure and consequent ext4 problems
Date: Mon, 12 Sep 2022 15:09:24 -0400 [thread overview]
Message-ID: <87fsgw8l15.fsf@vps.thesusis.net> (raw)
In-Reply-To: <CAJJqR23+V1_DTzYQv7=6M9U6qbd7yEHE3WR2XuXbaBH2oVqLQw@mail.gmail.com>
Luigi Fabio <luigi.fabio@gmail.com> writes:
> Well, I found SOMETHING of decided interest: when I run dumpe2fs with
> any backup superblock, this happens:
>
> ---
> Filesystem created: Tue Nov 4 08:56:08 2008
> Last mount time: Thu Aug 18 21:04:22 2022
> Last write time: Thu Aug 18 21:04:22 2022
> ---
>
> So the backups have not been updated since boot-before-last? That
> would explain why, when fsck tries to use those backups, it comes up
> with funny results.
That's funny. IIRC, the backups virtually never get updated. The only
thing e2fsck needs to get from them is the location of the inode tables
and block groups, and that does not change during the life of the
filesystem.
I might have something tickling the back of my memory that when e2fsck
is run, it updates the first backup superblock, but the others never got
updated.
next prev parent reply other threads:[~2022-09-12 19:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 14:51 RAID5 failure and consequent ext4 problems Luigi Fabio
2022-09-08 17:23 ` Phil Turmel
2022-09-09 20:32 ` Luigi Fabio
2022-09-09 21:01 ` Luigi Fabio
2022-09-09 21:48 ` Phil Turmel
2022-09-09 22:11 ` David T-G
2022-09-09 22:50 ` Luigi Fabio
2022-09-09 23:04 ` Luigi Fabio
2022-09-10 1:29 ` Luigi Fabio
2022-09-10 15:18 ` Phil Turmel
2022-09-10 19:30 ` Luigi Fabio
2022-09-10 19:55 ` Luigi Fabio
2022-09-10 20:12 ` Luigi Fabio
2022-09-10 20:15 ` Phil Turmel
2022-09-10 20:14 ` Phil Turmel
2022-09-10 20:17 ` Phil Turmel
2022-09-10 20:24 ` Luigi Fabio
2022-09-10 20:54 ` Luigi Fabio
2022-09-12 19:09 ` Phillip Susi [this message]
2022-09-13 3:58 ` Luigi Fabio
2022-09-13 12:47 ` Phillip Susi
2022-09-12 19:06 ` Phillip Susi
2022-09-13 4:02 ` Luigi Fabio
2022-09-13 12:51 ` Phillip Susi
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=87fsgw8l15.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=linux-raid@vger.kernel.org \
--cc=luigi.fabio@gmail.com \
--cc=philip@turmel.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