Date: Sat, 11 Jan 1997 23:52:41 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: mount -o async on a news servre Message-ID: <Mutt.19970111235241.j@uriah.heep.sax.de> In-Reply-To: <199701111952.MAA24055@phaeton.artisoft.com>; from Terry Lambert on Jan 11, 1997 12:52:34 -0700 References: <Mutt.19970111123319.j@uriah.heep.sax.de> <199701111952.MAA24055@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Terry Lambert wrote: > > Huh? You mean, after a successful umount, i could not eject a > > removable medium? I've never seen this, and i'm occasionally using a > > MO drive. Not only that i could remove it after umounting, my `od' > > driver even runs with the option to spin down the cartridge after > > closing, so i would `hear' if the drive were still open. > The buffers for the device are not decommitted until the next vclean > run, ... Perhaps they are not _guaranteed_ to be decommitted until the next vclean run? No, i don't think so. umount(8) waits until all buffers are clear, which often can take a tremendous amount of time on a MO medium. Once umount(8) returns, the medium spins down immediately, which basically means odclose() has been called. This proves your theory wrong. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970111235241.j>