From: David T-G <davidtg-robot@justpickone.org>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 failure and consequent ext4 problems
Date: Fri, 9 Sep 2022 22:11:18 +0000 [thread overview]
Message-ID: <20220909221118.GG7367@jpo> (raw)
In-Reply-To: <df503250-7c8e-d6f7-21fd-2fe4f1cae961@turmel.org>
Phil & Luigi, et al --
...and then Phil Turmel said...
%
...
%
% You haven't mentioned whether your --create operations specified
% --assume-clean.
He hasn't?
%
% On 9/9/22 17:01, Luigi Fabio wrote:
...
% >
% > On Fri, Sep 9, 2022 at 4:32 PM Luigi Fabio <luigi.fabio@gmail.com> wrote:
% > >
...
% > > > But I'll be brutally honest: your data is likely toast.
% > > Well, let's hope it isn't. All mdadm commands were -o and
% > > --assume-clean, so in theory the only thing which HAS been written are
% > > the md blocks, unless I am mistaken and/or I read the docs
% > > incorrectly?
...
% > > This is the list of --create and --assemble commands from the 6th
...
% > > 9813 mdadm --assemble /dev/md123 missing
% > > 9814 mdadm --assemble /dev/md123 missing /dev/sdf1 /dev/sdg1
...
% > > 9815 mdadm --assemble /dev/md123 /dev/sdf1 /dev/sdg1 /dev/sdk1
...
% > > /dev/sdm1
% > > 9823 mdadm --create -o -n 12 -l 5 /dev/md124 missing /dev/sde1
...
% > > 9824 mdadm --create -o -n 12 -l 5 /dev/md124 missing /dev/sde1
...
% > > 9852 mdadm --create -o --assume-clean -n 12 -l 5 --metadata=0.90
...
% > > 9863 mdadm --create -o --assume-clean -n 12 -l 5 --metadata=0.90
...
% > > 9879 mdadm --create -o --assume-clean -n 12 -l 5 --metadata=0.90
...
% > > 9889 mdadm --create -o --assume-clean -n 12 -l 5 --metadata=0.90
...
% > > 9892 mdadm --create -o --assume-clean -n 12 -l 5 --metadata=0.90
...
% > > 9895 mdadm --create -o --assume-clean -n 12 -l 5 --metadata=0.90
...
% > > 9901 mdadm --assemble /dev/md123 /dev/sdn1 /dev/sde1 /dev/sdf1
...
% > > 9903 mdadm --create -o --assume-clean -n 12 -l 5 --metadata=0.90
...
% > >
% > > Note that they all were -o, therefore if I am not mistaken no parity
% > > data was written anywhere. Note further the fact that the first two
% > > were the 'mistake' ones, which did NOT have --assume-clean (but with
% > > -o this shouldn't make a difference AFAIK) and most importantly the
% > > metadata was the 1.2 default AND they were the wrong array in the
% > > first place.
[snip]
I certainly don't know what I'm talking about, so this is all I'll say,
but it looked reasonably complete to me ...
HTH & HANW
:-D
--
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
next prev parent reply other threads:[~2022-09-09 22:11 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 [this message]
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
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=20220909221118.GG7367@jpo \
--to=davidtg-robot@justpickone.org \
--cc=linux-raid@vger.kernel.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