From: Roman Mamedov <rm@romanrm.net>
To: Phil Turmel <philip@turmel.org>
Cc: Eli Ben-Shoshan <eli@benshoshan.com>,
linux-raid@vger.kernel.org, John Stoffel <john@stoffel.org>
Subject: Re: Accidentally resized array to 9
Date: Sat, 30 Sep 2017 21:29:11 +0500 [thread overview]
Message-ID: <20170930212911.68547509@natsu> (raw)
In-Reply-To: <de7d94b2-7d2c-1419-420d-65b6f531c37f@turmel.org>
On Sat, 30 Sep 2017 12:21:20 -0400
Phil Turmel <philip@turmel.org> wrote:
> > Ideally what you can hope for, is you would get the bulk of array data intact,
> > only with the first 9 KB of each device *(8-2), so about the first 54 KB of
> > data on the md array, corrupted and unusable. It is likely the LVM and
> > filesystem tools will not recognize anything due to that, so you will need to
> > use some data recovery software to look for and save the data.
> >
>
> I agree with Roman. Most of your array should be still on the 8-disk
> layout. But you were mounted and had writing processes immediately
> after the broken grow, so there's probably other corruption due to
> writes on the 9-disk pattern in the 8 disks.
Adding one afterthought that I had, you could probably salvage the 54 KB in
question by reading them in (and saving to a file) from the current
"9-device array of 9KB devices" that you got.
With respect,
Roman
next prev parent reply other threads:[~2017-09-30 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 4:23 Accidentally resized array to 9 Eli Ben-Shoshan
2017-09-29 12:38 ` John Stoffel
2017-09-29 14:47 ` Eli Ben-Shoshan
2017-09-29 19:33 ` John Stoffel
2017-09-29 21:04 ` Eli Ben-Shoshan
2017-09-29 21:17 ` John Stoffel
2017-09-29 21:49 ` Eli Ben-Shoshan
2017-09-29 12:55 ` Roman Mamedov
2017-09-29 14:53 ` Eli Ben-Shoshan
2017-09-29 19:50 ` Roman Mamedov
2017-09-30 16:21 ` Phil Turmel
2017-09-30 16:29 ` Roman Mamedov [this message]
2017-09-30 23:30 ` John Stoffel
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=20170930212911.68547509@natsu \
--to=rm@romanrm.net \
--cc=eli@benshoshan.com \
--cc=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).