From: martin.kihlgren@adocca.com
To: linux-raid@vger.kernel.org
Cc: neilb@suse.de
Subject: Please help me save my data
Date: Fri, 8 Sep 2006 15:26:22 +0200 (CEST) [thread overview]
Message-ID: <57786.213.136.43.252.1157721982.squirrel@webmail.adocca.com> (raw)
Hello list.
I have a spot of trouble with a RAID5 array of mine, and I thought maybe
you could help me.
This is the story so far:
* I bought 10 external USB drives. This seemed like a good idea, they are
cheap, they are hot-pluggable and they are fast enough.
* I set them up in two RAID5 arrays, which I set up as LVM pv's. Then I
created an LVM vg out of these and an LVM lv out of the vg.
* I encrypted this lv and formatted it with an xfs fs.
This all worked perfectly fine, until I realized how bad these drives and
this USB controller work with ehci_hcd.
In short, the devices get reset all the time. And each time they get
reset, everything stops for a while. Nothing strange and no showstopper
here.
But the really bad thing is when they reset in some extra-bad way, and get
dropped completely. What happens then is that the RAID5 system drops them,
and they get reincarnated with a new device name. /dev/sdi becomes
suddenly /dev/sdn or something similarly horrbile.
And since I (up until yesterday) didnt know about write-intent bitmaps
each resync took around 10 hours. Plenty of time for ANOTHER disk to fail
and get dropped.
This I usually solved by doing mdadm -S and then mdadm -A -f.
Yesterday, however, I was feeling extra clever, and I just did mdadm -a
/dev/md1 /dev/sdn1.
This was a huge mistake.
What had happened, I now realized, was this:
* /dev/md1 is fine
* /dev/sdX1 drops, and /dev/md1 is degraded
* I re-add /dev/sdX1 in its new guise, and /dev/md1 is resyncing with
4 working drives and one spare
* /dev/sdY1 drops, and /dev/md1 stops
* I re-add /dev/sdY1 in its new guise, and mdadm marks it as a SPARE.
* I suddenly have an array with 3 working drives and 2 spares where
I know that one spare is in fact synced and ready to go, since
the array stopped the moment it failed.
Also, I dont know any longer WHERE in the array the synced but
spare-marked drive should go. I know that the working drives are 0, 2 and
4, but not where the synced spare drive should go.
So, what I want to do is:
* Mark the synced spare drive as working and in position 1
* Assemble the array without the unsynced spare and check if this
provides consistent data
* If it didnt, I want to mark the synced spare as working and in
position 3, and try the same thing again
* When I have it working, I just want to add the unsynced spare and
let it sync normally
* Then I will create a write-intent bitmap to avoid the dangerously
long sync times, and also buy a new USB controller hoping that it
will solve my problems
So, do you guys have any idea how I can do this? mdadm doesnt support
changing the superblock in such a free hand manner...
Please help me save this data :/ It is precious to me :.(
regards,
//Martin Kihlgren
next reply other threads:[~2006-09-08 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 13:26 martin.kihlgren [this message]
2006-09-09 16:00 ` Please help me save my data Tuomas Leikola
-- strict thread matches above, loose matches on Subject: below --
2006-09-08 13:36 martin.kihlgren
2006-09-11 12:16 martin.kihlgren
2006-09-11 13:10 ` Patrick Hoover
2006-09-16 13:14 ` Molle Bestefich
2006-09-16 23:53 ` martin.kihlgren
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=57786.213.136.43.252.1157721982.squirrel@webmail.adocca.com \
--to=martin.kihlgren@adocca.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).