On Sat, 06 Feb 2010 12:51:02 -0500 Doug Ledford <dledford@xxxxxxxxxx> wrote: > I will say that needing to touch multiple software packages might not be > a bad thing, but think of *how* they had to be changed. We had to add > special exceptions for mdmon all over the place: kernel scheduler (for > suspend/resume, mdmon can't be frozen like the rest of user space or > else writing our suspend to disk image doesn't work), initramfs, > initscripts after initramfs, initscripts on halt, SELinux. In all these > cases, we had to take something that we want to keep simple and add > special case rules and exceptions for mdmon. That pretty solidly says > that while this arrangement may have been elegant for *you*, it was not > elegant in the overall grand scheme of things. > or it just means we are breaking new ground :-) The suspend/resume issue you bring up is an important one and to my mind is currently unsolved. Based on my limited understanding of hibernation, I think that mdmon should be to quiesce (but not actually be frozen) prior to taking the in-memory snapshot, then thawed prior to writing that snapshot out to disk. Further when it is thawed after resume-from-disk it needs to know it has been thawed so it can check the metadata on-disk to see if any failure happened while it slept. Similar thing would be needed for suspend through fuse. Do you know exactly what was done to the scheduler in redhat? NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
