[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <77a58302766cb6c8fac45682ede63569df80cd5d.camel@hammerspace.com>
Date: Wed, 21 Feb 2024 13:48:19 +0000
From: Trond Myklebust <trondmy@...merspace.com>
To: "chuck.lever@...cle.com" <chuck.lever@...cle.com>, "zhitao.li@...rtx.com"
<zhitao.li@...rtx.com>, "tom@...pey.com" <tom@...pey.com>, "anna@...nel.org"
<anna@...nel.org>, "Dai.Ngo@...cle.com" <Dai.Ngo@...cle.com>,
"jlayton@...nel.org" <jlayton@...nel.org>, "neilb@...e.de" <neilb@...e.de>,
"kolga@...app.com" <kolga@...app.com>
CC: "huangping@...rtx.com" <huangping@...rtx.com>, "linux-nfs@...r.kernel.org"
<linux-nfs@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.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]
On Wed, 2024-02-21 at 16:20 +0800, Zhitao Li wrote:
> [You don't often get email from zhitao.li@...rtx.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@...merspace.com
Powered by blists - more mailing lists