Dan Williams (dan.j.williams@xxxxxxxxx) said: > It is not just setting writable, mdmon is also there to clear the bit > when writes have quiesced. Let me just see if I understand this infrastructure correctly. - device is set writable - kernel tells userspace - userspace frobs bit in superblock to say 'I want to be dirty!' - userspace tells kernel - kernel writes bit to disk ... stuff happens ... - userspace tells kernel to unmount, or remount R/O - kernel tells userspace "hey, i unmounted this" (userspace freaks out because the filesystem the daemon is running on just went away) - userspace frobs bit in superblock to say 'This array is CLEAN!' - userspace tells kernel - kernel writes bit to disk Is that really how it's supposed to work? So, why isn't the ext* journal or filesystem unclean flag handled via a userspace file monitoring daemon, then? Bill -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
