Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp678605ybl; Wed, 29 Jan 2020 07:47:30 -0800 (PST) X-Google-Smtp-Source: APXvYqyI7r1AfnAdYRg8QzzjR4Zt4BIP/1VCjfo9dxvAtaKq4DM8gPF7qUHCEY2epWP3FuV/xMGZ X-Received: by 2002:aca:cf12:: with SMTP id f18mr6854583oig.81.1580312850679; Wed, 29 Jan 2020 07:47:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580312850; cv=none; d=google.com; s=arc-20160816; b=eIHw8BPO344e1LiYSnPt0jSs5m0lOY+lE7Ya7qsSVlCv4rB887SYiyo7yVNGVxcU+w Xrea9tzm3jSAqBxD+zOXUtqYFET+gWMRVj/YibggjJwImNsT5r1Azf3hZnpQdEcuwg7/ HU2i6LaTc4V+UO5C0s7dXmkwzu29p4JtqRhPROecmSfp4mdxdzOdmkpmfPnSEyWxFO83 8X3OlIQZXHBmNx9jWkCKl0PZUqvmnyCFQ5l0aSfQSLTiSU3OwGIpQ1MRjC3eS2htWfs9 FH1A7AgZt9o2YYg8d+nZnF5e7YO/goNIw2csguZDG8VQnH78eUwlwY38AUYaxGsAU3PN b8XA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:to:from :dkim-signature; bh=xmS5cJ70b8059t69VzCcVW7xFuXd/e/NtOVGp4Hf8UQ=; b=mJvip+EeVG2Sc/mgM4IfRdH369EB1wil91qHu6YQrQAKxMEBT08ZfM+a1pVlzs53XL EDy95i2a+aTt6BxewwnhO3Tfoe4v0qKY2liCWntwqODvk53K/varjgMVYrWEZgDIcBFg D10ATFwean5QH2UN1iU3rVtG/uGqS6it6QZGf14GeLRRysxb8YezQCDjXv9Q/TGyLvby XwyBFRYfXjR+2JCup0Buoe+sPN6MEXCxDSLl2qDJPBDZrEY1oiJEm5b/gMlEwKKnqMl5 wXdR66ZjljVoq8T9muc2I1BPT2CxCJpSLsWgUp5WwEkqPx14c4xqy4EBZmLboAXRPrxl 4hbw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Y2z43ng1; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t25si1280555oic.183.2020.01.29.07.47.13; Wed, 29 Jan 2020 07:47:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Y2z43ng1; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726648AbgA2PrK (ORCPT + 99 others); Wed, 29 Jan 2020 10:47:10 -0500 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:39475 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726643AbgA2PrK (ORCPT ); Wed, 29 Jan 2020 10:47:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1580312829; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xmS5cJ70b8059t69VzCcVW7xFuXd/e/NtOVGp4Hf8UQ=; b=Y2z43ng1PZnsPB+5aaHTkyW7l6U2CNCRYaI7qsOG6KY7UCwY/4MhExbhZFsYOdOsrOY1zj g14Gm2WcBnDPEytru5DWLoTfXfsS0T3bFV8Inn6uqZmwdQb22APC6dRoEPPr948QUAB/+N FKS27Df5u94g/aRaGFTm0nX5sFwSKE0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-37-muW5GPGgMY6ryp2VGaqqKA-1; Wed, 29 Jan 2020 10:47:07 -0500 X-MC-Unique: muW5GPGgMY6ryp2VGaqqKA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9E2B58010D8 for ; Wed, 29 Jan 2020 15:47:06 +0000 (UTC) Received: from madhat.boston.devel.redhat.com (madhat.boston.devel.redhat.com [10.19.60.33]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5CBB2CFDEC for ; Wed, 29 Jan 2020 15:47:06 +0000 (UTC) From: Steve Dickson To: Linux NFS Mailing list Subject: [PATCH 2/2] manpage: Add a description of the 'softreval' / 'nosoftreval' mount option Date: Wed, 29 Jan 2020 10:47:03 -0500 Message-Id: <20200129154703.6204-2-steved@redhat.com> In-Reply-To: <20200129154703.6204-1-steved@redhat.com> References: <20200129154703.6204-1-steved@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Content-Transfer-Encoding: quoted-printable Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org From: Trond Myklebust Add a description of the 'softreval' / 'nosoftreval' mount options on the 'nfs' generic manpage. Signed-off-by: Trond Myklebust Signed-off-by: Steve Dickson --- utils/mount/nfs.man | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man index 84462cd..6f79c63 100644 --- a/utils/mount/nfs.man +++ b/utils/mount/nfs.man @@ -121,6 +121,36 @@ option may mitigate some of the risks of using the .B soft option. .TP 1.5i +.BR softreval " / " nosoftreval +In cases where the NFS server is down, it may be useful to +allow the NFS client to continue to serve up paths and +attributes from cache after +.B retrans +attempts to revalidate that cache have timed out. +This may, for instance, be helpful when trying to unmount a +filesystem tree from a server that is permanently down. +.IP +It is possible to combine +.BR softreval +with the +.B soft +mount option, in which case operations that cannot be served up +from cache will time out and return an error after +.B retrans +attempts. The combination with the default +.B hard +mount option implies those uncached operations will continue to +retry until a response is received from the server. +.IP +Note: the default mount option is +.BR nosoftreval +which disallows fallback to cache when revalidation fails, and +instead follows the behavior dictated by the +.B hard +or +.B soft +mount option. +.TP 1.5i .BR intr " / " nointr This option is provided for backward compatibility. It is ignored after kernel 2.6.25. --=20 2.21.1