Date: Sun, 12 Jan 1997 14:28:50 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mount -o async on a news servre Message-ID: <199701122128.OAA26338@phaeton.artisoft.com> In-Reply-To: <Mutt.19970112214006.j@uriah.heep.sax.de> from "J Wunsch" at Jan 12, 97 09:40:06 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Otherwise, everything works as expected. You can eject (or spin down) > > > the medium as soon as the umount completes. > > > The drive light does not go active until updated fires the writes; > > Then this must be TerryBSD. :-) In FreeBSD, umount(2) triggers the > buffer write (as David has explained you from a theoretical point of > view, and i tried to prove you from my own experience with my MO > drive). When I close a file, I schedule dirty buffers to be written. But I do not dissociate the inode from the vnode until that write has taken place because buffers are indexed by vnode/offset, not by device offset. If I do a bunch of writes, a close, and then a umount, there is a potential delay of the update time between the time the dirty buffer is written and the time it has successfully been reclaimed. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701122128.OAA26338>