linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pierre Vignéras" <pierre@vigneras.name>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm: failed devices become spares! -> Solved !
Date: Fri, 21 May 2010 23:27:49 +0200	[thread overview]
Message-ID: <201005212327.49734.pierre@vigneras.name> (raw)
In-Reply-To: <20100518120637.24d875c9@notabene.brown>

Sorry for the delay of my reply...

This small mail to let you know that my RAID array is currently recovering 
thanks to the valuable inputs of this mailing list users. You are great!

For the curious, what I did is the following:

# ##### Do not forget the '--assume-clean' as I almost did! ;-(
# mdadm -C /dev/md2 -l 10 -n 4 -c 64 -e 0.90 --assume-clean /dev/sdd1 missing 
/dev/sdc1 missing               
# vgchange -a y                                                                                               
# xfs_repair -n -t 1 -v /dev/my-vg/my-lv
# mount -o ro /dev/my-vg/my-lv /mnt/tmp
# find /mnt/tmp
# du -ks /mnt/tmp/
# umount /mnt/tmp
# #### Required: XFS asked the log to get replayed
# mount /dev/my-vg/my-lv /mnt/tmp/
# umount /mnt/tmp
# xfs_repair  -t 1 -v /dev/my-vg/my-lv
# mdadm --manage /dev/md2 --add /dev/sde1
# mdadm --manage /dev/md2 --add /dev/sdf1

The array is currently at 25 % of the recovery process. A bit too soon to say 
that everything is fine... By the way, I am quite sure now that my USB 
controllers (or the use driver or whatever in the chain except all disks) are 
buggy: all the other RAIDs of my setup are gone!

I will try to recover them using the same kind of process, to backup all data. 
Do you think that using BBR (since each time, the burden started due to a 
sector (write?) error), the problem will be "solved" (or at least postponed 
until BBR itself does not have enough free sectors)?

Anyway, again, thanks a lot to all of you. 
Open Source rocks! ;-)
-- 
Pierre Vignéras
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-05-21 21:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-16 15:40 mdadm: failed devices become spares! Pierre Vignéras
2010-05-16 19:56 ` Leslie Rhorer
2010-05-17 18:10   ` Pierre Vignéras
2010-05-17 21:09     ` Tim Small
2010-05-18  1:30     ` Neil Brown
2010-05-18  2:06       ` Neil Brown
2010-05-18 22:25         ` MRK
2010-05-19 19:56           ` Simon Matthews
2010-05-21 21:00           ` Pierre Vignéras
2010-05-21 21:27         ` Pierre Vignéras [this message]
2010-05-18 23:07       ` Pierre Vignéras
2010-05-19  1:45         ` Neil Brown

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=201005212327.49734.pierre@vigneras.name \
    --to=pierre@vigneras.name \
    --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).