From: Trond Myklebust <trondmy@hammerspace.com>
To: "chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"zhitao.li@smartx.com" <zhitao.li@smartx.com>,
"tom@talpey.com" <tom@talpey.com>,
"anna@kernel.org" <anna@kernel.org>,
"Dai.Ngo@oracle.com" <Dai.Ngo@oracle.com>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"neilb@suse.de" <neilb@suse.de>,
"kolga@netapp.com" <kolga@netapp.com>
Cc: "huangping@smartx.com" <huangping@smartx.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: NFS client IO fails with ERESTARTSYS when another mount point with the same export is unmounted with force [NFS] [SUNRPC]
Date: Wed, 21 Feb 2024 13:48:19 +0000 [thread overview]
Message-ID: <77a58302766cb6c8fac45682ede63569df80cd5d.camel@hammerspace.com> (raw)
In-Reply-To: <CAPKjjnrYvzH8hEk9boaBt-fETX3VD2cjjN-Z6iNgwZpHqYUjWw@mail.gmail.com>
On Wed, 2024-02-21 at 16:20 +0800, Zhitao Li wrote:
> [You don't often get email from zhitao.li@smartx.com. Learn why this
> is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi, everyone,
>
> - Facts:
> I have a remote NFS export and I mount the same export on two
> different directories in my OS with the same options. There is an
> inflight IO under one mounted directory. And then I unmount another
> mounted directory with force. The inflight IO ends up with "Unknown
> error 512", which is ERESTARTSYS.
>
All of the above is well known. That's because forced umount affects
the entire filesystem. Why are you using it here in the first place? It
is not intended for casual use.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2024-02-21 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 8:20 PROBLEM: NFS client IO fails with ERESTARTSYS when another mount point with the same export is unmounted with force [NFS] [SUNRPC] Zhitao Li
2024-02-21 13:48 ` Trond Myklebust [this message]
2024-02-22 3:05 ` Zhitao Li
2024-02-22 11:05 ` Jeff Layton
2024-02-22 15:20 ` Trond Myklebust
2024-02-23 3:44 ` Zhitao Li
2024-02-23 10:31 ` Jeff Layton
2024-02-27 2:35 ` Zhitao Li
2024-02-23 3:20 ` Zhitao Li
2024-02-27 23:55 ` NeilBrown
2024-02-28 3:37 ` Zhitao Li
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=77a58302766cb6c8fac45682ede63569df80cd5d.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=huangping@smartx.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.com \
--cc=zhitao.li@smartx.com \
/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