Forced unmount is used in a casual way to some degree by our team. We will adjust the usage of forced unmount and multiple mount points for the same export. As you said, all of the above is well known. Actually, this phenomenon is unexpected for us. Could you give some more information? Are they issues? And if they are issues, is there any plan to fix them? Best regards, Zhitao Li, in SmartX. On Wed, Feb 21, 2024 at 9:48 PM Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote: > > On Wed, 2024-02-21 at 16:20 +0800, Zhitao Li wrote: > > [You don't often get email from zhitao.li@xxxxxxxxxx. 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@xxxxxxxxxxxxxxx > >
