From: Phil Turmel <philip@turmel.org>
To: Luigi Fabio <luigi.fabio@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 failure and consequent ext4 problems
Date: Sat, 10 Sep 2022 16:14:14 -0400 [thread overview]
Message-ID: <10e92155-0662-44ca-87b0-16dbdb2efca4@turmel.org> (raw)
In-Reply-To: <CAJJqR23+V1_DTzYQv7=6M9U6qbd7yEHE3WR2XuXbaBH2oVqLQw@mail.gmail.com>
Hi Luigi,
On 9/10/22 15:55, Luigi Fabio wrote:
> 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.
Interesting.
> Is this ...as intended, I wonder? Does it also imply that any file
> that was written to > aug 18th will be in an indeterminate state? That
> would seem to be the implication.
Hmm. I wouldn't have thought so, but maybe the backup blocks don't get
updated as often?
{ I think you are about as far as I would have gotten myself, if I
allowed myself to get there. }
Phil
next prev parent reply other threads:[~2022-09-10 20:14 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 [this message]
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
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=10e92155-0662-44ca-87b0-16dbdb2efca4@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=luigi.fabio@gmail.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