Date: Wed, 19 Nov 2014 17:10:23 -0500 (EST) From: Benjamin Kaduk <kaduk@MIT.EDU> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: suspending threads before devices Message-ID: <alpine.GSO.1.10.1411191709140.19231@multics.mit.edu> In-Reply-To: <1580793.3ynJAbfVom@ralph.baldwin.cx> References: <201203202037.q2KKbNfK037014@svn.freebsd.org> <201411181721.56505.jhb@freebsd.org> <87FFDA99-ADDC-4F56-A3E8-56CCAA544542@bsdimp.com> <1580793.3ynJAbfVom@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Nov 2014, John Baldwin wrote: > Yes, there should have been quotes around unmount. I want a > VFS_SUSPEND/VFS_RESUME that for local filesystems (e.g. UFS) does the on-disk > equivalent of unmount. (Flush dirty buffers and mark filesystem as clean.) > You really want this for S4 and even for S3 so you don't have to fsck if > resume fails. BTW, I think for network or userland filesystems you just punt > on this (i.e. VFS_SUSPEND is a no-op or best-effort at most) Well, some network filesystems have things that could be done in this vein, but that would have to be at the filesystem layer, not in the VFS, I think. (E.g., OpenAFS has "disconnected mode".) -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1411191709140.19231>