* mdadm incremental failed: md device busy
@ 2010-12-15 17:50 Spelic
2010-12-15 18:50 ` Spelic
0 siblings, 1 reply; 2+ messages in thread
From: Spelic @ 2010-12-15 17:50 UTC (permalink / raw)
To: linux-raid
Hi there
this happened:
# cat /proc/mdstat
...other arrays not including sdb3...
md2 : active raid1 sda3[0]
52428728 blocks super 1.2 [2/1] [U_]
bitmap: 6/200 pages [24KB], 128KB chunk
...other arrays not including sdb3...
strangely sdb3 was not added to array at boot, I am still investigating
that, but now see this:
# mdadm --incremental /dev/sdb3
mdadm: failed to open /dev/md2: Device or resource busy.
#strace mdadm --incremental /dev/sdb3
...lots of stuff, then...
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
nanosleep({0, 200000000}, NULL) = 0
open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource busy)
........
write(2, "mdadm: failed to open /dev/md2: "..., 57mdadm: failed to open
/dev/md2: Device or resource busy.
) = 57
hmmm... strange thing, I just booted and md2 is not even mounted...
but now see this:
# mdadm /dev/md2 --add /dev/sdb3
mdadm: re-added /dev/sdb3
worked perfectly!
So?
Bug?
Thank you
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: mdadm incremental failed: md device busy
2010-12-15 17:50 mdadm incremental failed: md device busy Spelic
@ 2010-12-15 18:50 ` Spelic
0 siblings, 0 replies; 2+ messages in thread
From: Spelic @ 2010-12-15 18:50 UTC (permalink / raw)
To: linux-raid
On 12/15/2010 06:50 PM, Spelic wrote:
> Hi there
> this happened:
>
> # cat /proc/mdstat
> ...other arrays not including sdb3...
> md2 : active raid1 sda3[0]
> 52428728 blocks super 1.2 [2/1] [U_]
> bitmap: 6/200 pages [24KB], 128KB chunk
> ...other arrays not including sdb3...
>
> strangely sdb3 was not added to array at boot, I am still
> investigating that, but now see this:
>
> # mdadm --incremental /dev/sdb3
> mdadm: failed to open /dev/md2: Device or resource busy.
>
>
> #strace mdadm --incremental /dev/sdb3
> ...lots of stuff, then...
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> nanosleep({0, 200000000}, NULL) = 0
> open("/dev/md2", O_RDWR|O_EXCL) = -1 EBUSY (Device or resource
> busy)
> ........
> write(2, "mdadm: failed to open /dev/md2: "..., 57mdadm: failed to
> open /dev/md2: Device or resource busy.
> ) = 57
>
>
> hmmm... strange thing, I just booted and md2 is not even mounted...
> but now see this:
>
> # mdadm /dev/md2 --add /dev/sdb3
> mdadm: re-added /dev/sdb3
>
> worked perfectly!
>
> So?
> Bug?
>
> Thank you
I add one detail: the drive probably had been kicked at boot because it
was non-fresh.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-12-15 18:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-12-15 17:50 mdadm incremental failed: md device busy Spelic
2010-12-15 18:50 ` Spelic
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).