From: Jeff Layton <jlayton@kernel.org>
To: linux-nfs <linux-nfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: nfs remounting regression in v6.5-rc1
Date: Tue, 01 Aug 2023 13:01:18 -0400 [thread overview]
Message-ID: <3aba8d909955253a4630f66d0f72ee35f103a948.camel@kernel.org> (raw)
I've hit a regression that crept in sometime after v6.5-rc1. If I have 2
NFS mounts on a client that are mounting 2 directories of the same
export, and then I remount one of them ro, the other will also flip to
being ro as well. For instance:
[vagrant@kdevops-nfs-default ~]$ sudo mount kdevops-nfsd:/export/fstests/kdevops-nfs-default/test /media/test
[vagrant@kdevops-nfs-default ~]$ sudo mount kdevops-nfsd:/export/fstests/kdevops-nfs-default/scratch /media/scratch
[vagrant@kdevops-nfs-default ~]$ mount -v | grep nfs
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
kdevops-nfsd:/export/fstests/kdevops-nfs-default/test on /media/test type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.79,local_lock=none,addr=192.168.122.138)
kdevops-nfsd:/export/fstests/kdevops-nfs-default/scratch on /media/scratch type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.79,local_lock=none,addr=192.168.122.138)
[vagrant@kdevops-nfs-default ~]$ sudo mount kdevops-nfsd:/export/fstests/kdevops-nfs-default/scratch /media/scratch -o remount,ro
[vagrant@kdevops-nfs-default ~]$ mount -v | grep nfs
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
kdevops-nfsd:/export/fstests/kdevops-nfs-default/test on /media/test type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.79,local_lock=none,addr=192.168.122.138)
kdevops-nfsd:/export/fstests/kdevops-nfs-default/scratch on /media/scratch type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.79,local_lock=none,addr=192.168.122.138)
In v6.4, /media/test stays rw. Mounting with -o nosharecache works
around the problem (since that disables superblock sharing). This also
manifests as a failure in fstest generic/306.
I'm running a bisect now to try and track down the problem, but if
anyone has thoughts on the cause, let me know.
Cheers,
--
Jeff Layton <jlayton@kernel.org>
reply other threads:[~2023-08-01 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3aba8d909955253a4630f66d0f72ee35f103a948.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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