From: Asdo <asdo@shiftmail.org>
To: Alex Boag-Munroe <boagenator@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: I am an idiot.
Date: Thu, 04 Mar 2010 13:25:08 +0100 [thread overview]
Message-ID: <4B8FA6A4.3040309@shiftmail.org> (raw)
In-Reply-To: <68c4f7e31003040330s21b6059ex6859247ff67b43e2@mail.gmail.com>
Alex Boag-Munroe wrote:
> Hi guys...
>
> Yes I am an idiot. I was changing the chunk size of my RAID5 array
> last night from 64kb to 256kb and left it running overnight. During
> the night we had a power outage.
>
> This is where the idiot part comes in. The backup file is on a
> filesystem that's part of the RAID5 array, so obviously I am unable to
> start it. I completely forgot the filesystem I specified for
> --backup-file was part of the same array.
>
> Once you're all done pointing and laughing, can you let me know if I
> am totally screwed? I've a lot of data here that I -really- don't
> want to lose...
>
> Please help..
>
> Idiot.
>
Firstly I will say that I have never faced this situation, so please
wait for someone more knowledgeable to reply before trying.
Supposing the resync cannot be continued after a power failure (which I
am not sure)...
My idea is that the reshape progresses linearly so one of the two
filesystems (either the original one or backup) should be accessible. If
the power failed when the reshape was within the first filesystem, the
second filesystem should be somehow accessible, if it failed when the
reshape was within the second filesystem, the first filesystem should be
somehow accessible.
In this situation I guess you need to go to the hard route: you will
probably need to recreate the array with all the drives specified
exactly in the same order, using all the original options (you can get
info from every drive with mdadm --examine /dev/sdXY), and the chunksize
either set at 64k or at 256k (you try both), and specifying
--assume-clean so that it does not start to resync, and then set it
--readonly before doing anything else. Then you will probably be able to
do some experiments try mounting one of the two filesystems.
Thinking again, I guess there is a situation which will prevent you to
see both filesystems... this is the case if 64kb prevents you to see the
good filesystem and 256k prevents you to see the LVM metadata :-( You
use LVM right? In this case you might need to "find" your filesystem by
mounting the device with progressively increasing offsets from the
beginning, without the help of LVM. And this will work only if your good
partition in LVM was contiguous (LVM allows holes).
Anyway, wait other replies.
Good luck
Asdo
prev parent reply other threads:[~2010-03-04 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 11:30 I am an idiot Alex Boag-Munroe
2010-03-04 12:01 ` John Robinson
2010-03-04 12:22 ` Alex Boag-Munroe
2010-03-04 12:23 ` Alex Boag-Munroe
2010-03-04 12:25 ` Majed B.
2010-03-04 20:45 ` I am an idiot. (power failure during chunk resize, no backup file) Neil Brown
2010-03-04 12:25 ` Asdo [this message]
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=4B8FA6A4.3040309@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=boagenator@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).