* Changed fstype for nfs4 mounts starting with 5.6-rc1 (bisected)
@ 2020-02-18 10:46 Patrick Steinhardt
0 siblings, 0 replies; only message in thread
From: Patrick Steinhardt @ 2020-02-18 10:46 UTC (permalink / raw)
To: linux-nfs
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Hi,
starting with v5.6-rc1, I've noticed that my shutdown scripts do not
work properly anymore in case there's any NFS4 mounts present. The issue
stems from an fstype change: while NFS4 mounts previously had fstype
"nfs4", they now have type "nfs". As a result, my "umount -at nfs4"
doesn't do anything, resulting in a hang later on.
While this can trivially be fixed on my side by doing "umount -at
nfs,nfs4", I guess that this was an involuntary change. A bisect points
to commit f2aedb713c28 (NFS: Add fs_context support., 2019-12-10).
Reproducer:
$ mount.nfs4 host:/mnt /mnt
$ findmnt -otarget,source,fstype /mnt
TARGET SOURCE FSTYPE
/mnt host:/mnt nfs
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-02-18 10:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-02-18 10:46 Changed fstype for nfs4 mounts starting with 5.6-rc1 (bisected) Patrick Steinhardt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.