From: Bill Nottingham Subject: Re: [RFC PATCH 2/3] raid: external and internal metadata support Date: Fri, 6 Feb 2009 12:38:14 -0500 Message-ID: <20090206173814.GA3541@nostromo.devel.redhat.com> References: <20090206164019.GD552@redhat.com> <20090206165601.GF11144@nostromo.devel.redhat.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Dan Williams Cc: "Danecki, Jacek" , Jeremy Katz , "initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "neilb-l3A5Bk7waGM@public.gmane.org" Dan Williams (dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org) 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html