https://bugzilla.novell.com/show_bug.cgi?id=379745 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=379745#c8 --- Comment #8 from Neil Brown <nfbrown@novell.com> 2008-07-09 21:13:18 MDT --- Thanks. The evidence seems to point to the very last write to the device is getting lost. md writes out the bitmap header and then the raid metadata. So you the event counter in the bitmap header should normally be the same as that in the raid metadata, or one more if the bitmap header write succeeded but the metadata write didn't. We are seeing the bitmap metadata with 4144 and the raid metadata with 4145. There is a case where the event count goes backwards though. When a dirty array is being marked clean we sometimes step the event count backwards rather than forwards (there is a good reason...). It seems like that is happening here. This suggests that the update of the bitmap header works, but the update of the array metadata doesn't. I can't think of a really good way to get these writes to happen earlier. Possibly putting mount -o remount,ro / sync ; sync; sleep 1 in /etc/init.d/halh just before the last line: exec $command -d -f -n $opts might help. If md doesn't see any write activity for 200ms it marks the array clean. The above should allow that to happen 800ms before the machine is stopped. Can you try 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.