Date: Sun, 27 Jun 1999 22:18:22 -0400 (EDT) From: der Mouse <mouse@Rodents.Montreal.QC.CA> To: Francois-Rene Rideau <fare@tunes.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, NetBSD Kernel <tech-kern@netbsd.org>, OpenBSD Kernel <tech@openbsd.org>, Linux Kernel <linux-kernel@vger.rutgers.edu> Subject: Re: Improving the Unix API Message-ID: <199906280218.WAA00668@Twig.Rodents.Montreal.QC.CA>
next in thread | raw e-mail | index | archive | help
>> -f The filesystem is forcibly unmounted. Active special devices >> continue to work, but all other files return errors if further >> accesses are attempted. > I think that returning errors is WRONG, unless [...] > It means that you can't fix the problem with the filesystem and > resume operations nicely afterwards; I think I see part of the problem here. You are thinking "unmount to fix problem, will remount later". "umount -f" is more like "it's going away, dammit, and I'd rather crash a few processes than have to take down the whole system". It might be worthwhile having an option that causes attempted accesses to hang until the filesystem comes back online, somewhat akin to Auspex's filesystem "isolation". der Mouse mouse@rodents.montreal.qc.ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906280218.WAA00668>