https://bugzilla.novell.com/show_bug.cgi?id=793954
https://bugzilla.novell.com/show_bug.cgi?id=793954#c5
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
--- Comment #5 from Neil Brown 2013-02-07 03:27:05 UTC ---
Sorry, I've been very distracted throughout January.
Hopefully you didn't wait for me and have already re-integrated the missing
disk into the array. If not, feel free to do so.
The "unknown-block(8,3)" is strange. 8,3 is /dev/sda3. If Linux don't know
that, it suggests that sda has just been removed from in some way. It must
have been present previously else mdadm wouldn't have tried to use it in the
array.
The "return -16" means EBUSY. I'm surprised that a disappeared drive would
return EBUSY rather than EIO or ENODEV or similar, so I might be
misinterpreting something.
However it is clear that when md tries to access /dev/sda3 it cannot, either
because it doesn't exist any more, or because it is being used by something
else.
It might be possible that mdadm is racing with itself and another mdadm gets an
O_EXCL open on the device just as md tries to open it. That wouldn't explain
the "unknown-block(8,3)", but would explain the rest.
mdadm wasn't originally designed with concurrent access in mind and there have
been a few issues in that area of late. I'll see if I can come up with a
credible race scenario, then see if I can provide some locking against it.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.