78d093eaf5
sufficient to clobber this nasty little bug. The behaviour observed was a panic when doing a 'raidctl -f' on a component when DAGs were in flight for the given RAID set. Unfortunatly, the faulty behaviour was very intermittent, and it was difficult to not only reliably reproduce the bug (nor determine when it was fixed!) but also to even figure out what might be the cause of the problem. The real issue was that ci_vp for the failed component was being set to NULL in rf_FailDisk(), but with DAGs still in flight, some of them were still expecting to use ci_vp to determine where to read to/write from! The fix is to call rf_SuspendNewRequestsAndWait() from rf_FailDisk() to make sure the RAID set is quiet and all IOs have completed before mucking with ci_vp and other data structures. rf_ResumeNewRequests() is then used to continue on as usual. |
||
---|---|---|
bin | ||
contrib/sys | ||
crypto | ||
dist | ||
distrib | ||
doc | ||
etc | ||
games | ||
gnu | ||
include | ||
lib | ||
libexec | ||
regress | ||
rescue | ||
sbin | ||
share | ||
sys | ||
tools | ||
usr.bin | ||
usr.sbin | ||
x11 | ||
build.sh | ||
BUILDING | ||
Makefile | ||
Makefile.inc | ||
UPDATING |