https://bugzilla.novell.com/show_bug.cgi?id=379745
User nfbrown@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=379745#c21
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|nfbrown@novell.com |
--- Comment #21 from Neil Brown 2008-07-31 23:30:48 MDT ---
md will mark an array as clean about 200ms after the last write,
which will typcially happen when the filesystem is marked readonly.
Alternately, md will mark the array as clean when it is stopped.
This happens very late in the shutdown sequence by a reboot_notifier.
This is normally enough to mark the array clean properly.
If the reboot notifiers are not being run for some reason, or if
devices aren't flushed after md's reboot notifier (which has a priority
of INT_MAX and so should run first), then the marking of the array
as clean might not get to the device.
So it should all 'just work'. It isn't clear to me why it doesn't
"just work" in this situation.
You probably need to ask someone who understands cache flushing
with the particular devices in question.
If you send a SIGKILL to the md thread, e.g.
killall -9 md0_raid1
it will cause the array to be marked clean immediately after the last
write. This might help a little but isn't really a fix (more of value
for experimentation).
The real problem is that either the md rebot_notifier isn't being
run, or the device cache isn't being flushed after that.
--
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.