Date: Mon, 30 May 2011 16:07:51 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Robert Watson <rwatson@freebsd.org> Cc: svn-src-head@freebsd.org, Rick Macklem <rmacklem@freebsd.org>, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r222466 - head/sbin/umount Message-ID: <20110530130751.GV48734@deviant.kiev.zoral.com.ua> In-Reply-To: <alpine.BSF.2.00.1105301347380.60306@fledge.watson.org> References: <201105292113.p4TLDrA3046886@svn.freebsd.org> <alpine.BSF.2.00.1105301347380.60306@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--ESod/vG06iFAbj33 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 30, 2011 at 01:48:53PM +0100, Robert Watson wrote: > On Sun, 29 May 2011, Rick Macklem wrote: >=20 > > Modify the umount(8) command so that it doesn't do > > a sync(2) syscall before unmount(2) for the "-f" case. > > This avoids a forced dismount from getting stuck for > > an NFS mountpoint in sync() when the server is not > > responsive. With this commit, forced dismounts should > > normally work for the NFS clients, but can take up to > > about 1minute to complete. >=20 > I'm actually a bit confused about why umount(8) calls sync(2) at all:=20 > surely it's the responsibility of the file system, rather than the userla= nd=20 > tool, to ensure consistency subject to file system configuration and=20 > unmount-time flags? This call is from the same department as triple-sync before reboot, IMO. --ESod/vG06iFAbj33 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3jlqYACgkQC3+MBN1Mb4indgCgiMHk6ZWSIxLfz0jIPmCMLuGp VfcAn3Q+6CJGGt0CQ3CjYpr7KiSWDw8L =83zU -----END PGP SIGNATURE----- --ESod/vG06iFAbj33--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110530130751.GV48734>