From be596a353536ab64bc861846a598172257a2b89d Mon Sep 17 00:00:00 2001 From: rmacklem Date: Wed, 17 Jun 2015 23:24:46 +0000 Subject: 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. PR: 200585 MFC after: 3 days --- sbin/umount/umount.8 | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'sbin') diff --git a/sbin/umount/umount.8 b/sbin/umount/umount.8 index e62bcc5..2ddbf5a 100644 --- a/sbin/umount/umount.8 +++ b/sbin/umount/umount.8 @@ -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 unmounted. 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. -- cgit v1.1