From: NeilBrown <neilb@suse.de>
To: NFS <linux-nfs@vger.kernel.org>
Subject: Trailing '/' on path names in /etc/fstab confused mount.
Date: Fri, 7 Oct 2011 11:53:11 +1100 [thread overview]
Message-ID: <20111007115311.278a7acf@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
If I have:
host:/path /mountpoint nfs defaults 0 0
in /etc/fstab, mount then "mount /mountpoint" the entry that
appears in /proc/mounts is
host:/path/ /mountpoint nfs .....
Note the extra '/'.
This confused mount. If I run
mount -a -t nfs,nfs4 -f -v -n -i
(as I might in a script to check if all NFS mountpoints are actually mounted),
it thinks that /mountpoint is not correctly mounted. If I edit /etc/fstab
to put the '/' in, 'mount' is not confused any more and reports correctly.
So:
Why do we get the trailing '/'? Is it really needed or is it a bug?
If it is really needed I suspect we need to teach 'mount' to ignore such
things.... but is it guaranteed that requesting "/path/" from the server
is exactly the same as requesting "/path" ??? It certainly is for NFSv4
and any v3 server that handled the two differently could certainly be
considered to be odd, but is it definitely wrong?
Thought?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
reply other threads:[~2011-10-07 0:53 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=20111007115311.278a7acf@notabene.brown \
--to=neilb@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).