From: "Francisco Zafra" <fzafra@gmail.com>
To: 'Jim Radford' <jradford@npl.com>
Cc: linux-raid@vger.kernel.org
Subject: RE: Recovery raid5 after sata cable failure.
Date: Sun, 17 Jul 2005 14:52:24 +0200 [thread overview]
Message-ID: <42da54b9.09ba4632.7805.37b0@mx.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0507170520090.8523@hoss.npl.com>
Hi, I am using lvm in this system, but only for parallel ATA disks, that not
use raid system. Anyway I deactivated lvm units, and tried again to readd de
faulty drive with the same results:
root@Torero-2:~ # mdadm /dev/md0 -a /dev/sdh1
mdadm: Cannot open /dev/sdh1: Device or resource busy
Thanks,
Paco.
> -----Mensaje original-----
> De: Jim Radford [mailto:jradford@npl.com]
> Enviado el: domingo, 17 de julio de 2005 14:21
> Para: Francisco Zafra
> Asunto: Re: Recovery raid5 after sata cable failure.
>
> Francisco,
>
> I was having a simuliar issue, and it was due to the fact LVM
> was starting before the raid array was assembled, if you are
> using LVM you might want to check that the array is assembled
> before LVM starts. (Probably would be the same for EVMS also).
>
> Regards,
> Jim
>
>
> On Sun, 17 Jul 2005, Francisco Zafra wrote:
>
> > Hi all,
> >
> > I have raid5 array working without problem for some
> months. A SATA
> > cable failed and de raid5 works fine keeping the superblock
> > persistent, but now, I can't get the old device inserted
> into the array.
> > This is the array just now:
> >
> > root@Torero-2:/mnt/raid5 # mdadm --detail /dev/md0
> > /dev/md0:
> > Version : 00.90.01
> > Creation Time : Tue May 31 19:37:37 2005
> > Raid Level : raid5
> > Array Size : 1367507456 (1304.16 GiB 1400.33 GB)
> > Device Size : 195358208 (186.31 GiB 200.05 GB)
> > Raid Devices : 8
> > Total Devices : 7
> > Preferred Minor : 0
> > Persistence : Superblock is persistent
> >
> > Update Time : Sun Jul 17 13:06:17 2005
> > State : clean, degraded
> > Active Devices : 7
> > Working Devices : 7
> > Failed Devices : 0
> > Spare Devices : 0
> >
> > Layout : left-symmetric
> > Chunk Size : 512K
> >
> > UUID : c4ed8e45:2a036953:92bff479:7cf5bac9
> > Events : 0.162797
> >
> > Number Major Minor RaidDevice State
> > 0 8 1 0 active sync /dev/sda1
> > 1 8 17 1 active sync /dev/sdb1
> > 2 8 33 2 active sync /dev/sdc1
> > 3 8 49 3 active sync /dev/sdd1
> > 4 8 65 4 active sync /dev/sde1
> > 5 8 81 5 active sync /dev/sdf1
> > 6 8 97 6 active sync /dev/sdg1
> > 7 0 0 - removed
> >
> >
> > And I try to re-add the old disk in this way:
> >
> > root@Torero-2:/mnt/raid5 # mdadm /dev/md0 -a /dev/sdh1
> > mdadm: Cannot open /dev/sdh1: Device or resource busy
> >
> > What is wrong? What I am doing bad? Sdh1 is absolutely
> unused, so I
> > don't understand the error "resource busy"
> >
> > Thanks,
> >
> > Paco Zafra.
> >
> > -
> > 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
> >
>
> --
> ==============================================================
> ============
> Jim Radford <jradford@npl.com>
> http://www.jimradford.com/
> ==============================================================
> ============
>
next parent reply other threads:[~2005-07-17 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0507170520090.8523@hoss.npl.com>
2005-07-17 12:52 ` Francisco Zafra [this message]
2005-07-17 11:34 Recovery raid5 after sata cable failure Francisco Zafra
2005-07-17 22:10 ` Neil Brown
2005-07-18 8:36 ` Francisco Zafra
2005-07-18 9:40 ` Neil Brown
2005-07-18 9:56 ` Francisco Zafra
2005-07-18 10:15 ` Brad Campbell
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=42da54b9.09ba4632.7805.37b0@mx.gmail.com \
--to=fzafra@gmail.com \
--cc=jradford@npl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.