public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: linux-nfs@vger.kernel.org
Subject: Changed fstype for nfs4 mounts starting with 5.6-rc1 (bisected)
Date: Tue, 18 Feb 2020 11:46:05 +0100	[thread overview]
Message-ID: <20200218104605.GA281780@ncase> (raw)

[-- 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 --]

                 reply	other threads:[~2020-02-18 10:45 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=20200218104605.GA281780@ncase \
    --to=ps@pks.im \
    --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