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

[Killian De Volder <killian.de.volder@megasoft.be>]

The world thanks you. :)

Killian De Volder

On 11-08-14 02:40, NeilBrown wrote:
> On Sat, 09 Aug 2014 10:32:54 +0200 Killian De Volder
> <killian.de.volder@megasoft.be> wrote:
>
>> sdb2 worked ! (And sorry for not trying sdb2, mdadm asks for /dev/md? so you naturally write /dev/sd? for the disk thereafter too :) )
>> Now the question should -r failed work ?
> Yes it "should", but it appears that I broke it for mdadm 3.3.
> It'll be fixed in 3.3.2 by
>   http://git.neil.brown.name/?p=mdadm.git;a=commitdiff;h=b47024f1c5fde5d4fbc65807b9b29e06c056584e
> and a couple of prior commits.
>
> Thanks,
> NeilBrown
>
>
>> Killian De Volder
>>
>> On 09-08-14 10:23, NeilBrown wrote:
>>> On Sat, 09 Aug 2014 09:52:09 +0200 Killian De Volder
>>> <killian.de.volder@megasoft.be> wrote:
>>>
>>>> Doesn't work since sdb has been ejected. Strace below.
>>>>
>>>> package manager: mdadm 3.3-r2
>>>> #mdadm -V: mdadm - v3.3 - 3rd September 2013
>>>>
>>>> Just tried 3.3-r3 and 3.2.6-r1 same issue.
>>>> (There are no older in the package manager to try fast.)
>>>>
>>>> #strace mdadm /dev/md126 -r /dev/sdb2
>>> I note that you put "/dev/sdb2" on the end of the line.
>>>
>>>
>>>>> How about
>>>>>    mdadm /dev/md127 -r sdb2
>>> I note that I just put "sdb2" on the end of the line.  Perhaps I should have
>>> been explicit and say 'not "/dev/sdb2", just "sdb2"'.  It does make a
>>> difference.
>>>
>>> NeilBrown
>>>