Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory

[NeilBrown <neilb@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

On Sat, 09 Aug 2014 00:10:13 +0200 Killian De Volder
<killian.de.volder@megasoft.be> wrote:

> I'm having some trouble with a disk of unknown cause.
> As a result the disk is now "failed"
> 
> #dmesg
> [362288.463008] ata3: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
> ...
> [377997.666956] md: super_written gets error=-5, uptodate=0
> [377997.666960] md/raid1:md126: Disk failure on sdb3, disabling device
> 
> I replugged the disk, and added it again to the raid (it is now called sdf instead of sdb):
> 
> # cat /proc/mdstat:
> md126 : active raid1 sdf2[5] sdd2[0] sde2[3] sdc2[2] sdb2[4](F)
>       102272 blocks super 1.2 [4/4] [UUUU]
> 
> So I wanted to remove the failed disk:
> 
> # mdadm /dev/md126 -r failed
> mdadm: Cannot find 8:18: No such file or directory

Hmm.. that looks broken.
What version of mdadm is this?
Does
   mdadm /dev/md126 -r detached
work?
How about
   mdadm /dev/md127 -r sdb2

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]