In the XFS kernel tree v2.4.3 w/ several patches,
we were unable to "raidhotremove" and subsequently
"raidhotadd" a spare without a reboot. It did not
matter if you had a new or the same hard disk. We then
tried the patch Igno Molnar sent regarding the issue.
http://www.mail-archive.com/[email protected]/msg00551.html
This solved the problem of not doing a reboot and trying
to switch a hotspare and faulty drive.
In addition, however, we are seeing a kernel panic using
raid 5 when mdrecoveryd starts when after doing the hotspare
and faulty drive swap a second time without a reboot.
Sequence of events w/ the patch:
1) "raidsetfaulty" to a valid raid 5 disk
2) hotspare is incorporated correctly (resync starts)
3) "raidhotremove" and "raidhotadd" to get the
once "faulty" drive in as the new spare
4) after the new raid 5 is completely finished
syncying, "raidsetfaulty" one of the new raid
5 valid drives
5) a kernel panic with the start of mdrecoveryd
using the old valid drive which is now the new
hot spare.
Result: the resync freezes although the rest of
the system is useable and fine. A reboot fixes
the issue.
Do you have any suggestions Neil?
thanks, Scott
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
