RE: Recovery raid5 after sata cable failure.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday July 18, fzafra@xxxxxxxxx wrote:
> I already tried that:
> 
> root@Torero-2:~ # cat /proc/mdstat
> Personalities : [linear] [raid5] 
> md0 : active raid5 sdg1[6] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
>       1367507456 blocks level 5, 512k chunk, algorithm 2 [8/7] [UUUUUUU_]
>       
> unused devices: <none>
> root@Torero-2:~ # mdadm /dev/md0 -r /dev/sdh1
> mdadm: hot remove failed for /dev/sdh1: No such device or address
> root@Torero-2:~ # mdadm /dev/md0 -a /dev/sdh1
> mdadm: Cannot open /dev/sdh1: Device or resource busy


Uhm, you might have a buggy version of mdadm.  If you have 1.10.0, get
an upgrade.

Otherwise either sdh1 or sdh must be:
  open by some process with O_EXCL
  open via a /dev/raw/* device
  part of an md device (which it obviously isn't)
  part of a dm device
  mounted as a filesystem
  an external-journal device for a jfs or ext3 or xfs filesystem
  in use as a swap device
  open for writing under a security level of 1 (whatever that means..)
  an mtd device that is open

(those are all the places that I can find that take an exclusive lock
 on a block device).

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux