From: Steve Dickson <SteveD@redhat.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] intr/nointr are ignored now
Date: Thu, 13 Mar 2014 11:15:20 -0400 [thread overview]
Message-ID: <5321CB88.6060704@RedHat.com> (raw)
In-Reply-To: <1394587065-27513-1-git-send-email-rees@umich.edu>
On 03/11/2014 09:17 PM, Jim Rees wrote:
> Signed-off-by: Jim Rees <rees@umich.edu>
> ---
> utils/mount/nfs.man | 51 ++++-----------------------------------------------
> 1 file changed, 4 insertions(+), 47 deletions(-)
Committed...
steved.
>
> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
> index ef09a31..fe4f9b1 100644
> --- a/utils/mount/nfs.man
> +++ b/utils/mount/nfs.man
> @@ -125,6 +125,10 @@ option may mitigate some of the risks of using the
> .B soft
> option.
> .TP 1.5i
> +.BR intr " / " nointr
> +This option is provided for backward compatibility.
> +It is ignored after kernel 2.6.25.
> +.TP 1.5i
> .BI timeo= n
> The time in deciseconds (tenths of a second) the NFS client waits for a
> response before it retries an NFS request.
> @@ -668,30 +672,6 @@ Using the
> option is also required when mounting exports on NFS servers
> that do not support the NLM protocol.
> .TP 1.5i
> -.BR intr " / " nointr
> -Selects whether to allow signals to interrupt file operations
> -on this mount point. If neither option
> -is specified (or if
> -.B nointr
> -is specified),
> -signals do not interrupt NFS file operations. If
> -.B intr
> -is specified, system calls return EINTR if an in-progress NFS operation is interrupted by
> -a signal.
> -.IP
> -Using the
> -.B intr
> -option is preferred to using the
> -.B soft
> -option because it is significantly less likely to result in data corruption.
> -.IP
> -The
> -.BR intr " / " nointr
> -mount option is deprecated after kernel 2.6.25.
> -Only SIGKILL can interrupt a pending NFS operation on these kernels,
> -and if specified, this mount option is ignored to provide backwards
> -compatibility with older kernels.
> -.TP 1.5i
> .BR cto " / " nocto
> Selects whether to use close-to-open cache coherence semantics.
> If neither option is specified (or if
> @@ -807,29 +787,6 @@ The mount request fails if the server's rpcbind service is not available,
> the server's NFS service is not registered with its rpcbind service,
> or the server's NFS service is not available on the advertised port.
> .TP 1.5i
> -.BR intr " / " nointr
> -Selects whether to allow signals to interrupt file operations
> -on this mount point. If neither option is specified (or if
> -.B intr
> -is specified), system calls return EINTR if an in-progress NFS operation
> -is interrupted by a signal. If
> -.B nointr
> -is specified, signals do not
> -interrupt NFS operations.
> -.IP
> -Using the
> -.B intr
> -option is preferred to using the
> -.B soft
> -option because it is significantly less likely to result in data corruption.
> -.IP
> -The
> -.BR intr " / " nointr
> -mount option is deprecated after kernel 2.6.25.
> -Only SIGKILL can interrupt a pending NFS operation on these kernels,
> -and if specified, this mount option is ignored to provide backwards
> -compatibility with older kernels.
> -.TP 1.5i
> .BR cto " / " nocto
> Selects whether to use close-to-open cache coherence semantics
> for NFS directories on this mount point.
>
prev parent reply other threads:[~2014-03-13 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 1:17 [PATCH] intr/nointr are ignored now Jim Rees
2014-03-13 15:15 ` Steve Dickson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5321CB88.6060704@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).