Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Jun 2015 23:15:57 +0000 (UTC)
From:      Rick Macklem <rmacklem@FreeBSD.org>
To:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-10@freebsd.org
Subject:   svn commit: r284652 - stable/10/sbin/umount
Message-ID:  <201506202315.t5KNFv0C034436@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: rmacklem
Date: Sat Jun 20 23:15:57 2015
New Revision: 284652
URL: https://svnweb.freebsd.org/changeset/base/284652

Log:
  MFC: r284531
  Document that a forced dismount of an NFSv3 mount when the
  NLM (rpc.lockd) is running can crash the system.
  Unfortunately this is not easy to fix, but I have left
  PR#200585 open.

Modified:
  stable/10/sbin/umount/umount.8
Directory Properties:
  stable/10/   (props changed)

Modified: stable/10/sbin/umount/umount.8
==============================================================================
--- stable/10/sbin/umount/umount.8	Sat Jun 20 22:24:44 2015	(r284651)
+++ stable/10/sbin/umount/umount.8	Sat Jun 20 23:15:57 2015	(r284652)
@@ -28,7 +28,7 @@
 .\"     @(#)umount.8	8.2 (Berkeley) 5/8/95
 .\" $FreeBSD$
 .\"
-.Dd November 22, 2014
+.Dd June 17, 2015
 .Dt UMOUNT 8
 .Os
 .Sh NAME
@@ -81,6 +81,9 @@ The root file system cannot be forcibly 
 For NFS, a forced dismount can take up to 1 minute or more to
 complete against an unresponsive server and may throw away
 data not yet written to the server for this case.
+Also, doing a forced dismount of an NFSv3 mount when
+.Xr rpc.lockd 8
+is running is unsafe and can result in a crash.
 .It Fl h Ar host
 Only file systems mounted from the specified host will be
 unmounted.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201506202315.t5KNFv0C034436>