From: Chip Salzenberg <chip@pobox.com>
To: Nitin Chandrachoodan <nitin@tenet.res.in>
Cc: nfs@lists.sourceforge.net
Subject: Re: remount error: 'unknown nfs mount option: v3'
Date: Tue, 29 Jul 2003 15:06:03 -0700 [thread overview]
Message-ID: <20030729220602.GA18733@perlsupport.com> (raw)
In-Reply-To: <20030728063639.GD2204@tenet.res.in>
According to Nitin Chandrachoodan:
> mount -n -o remount,rw /
> mount -n -o remount,rw /usr
>
> the second mount fails with "unknown nfs mount option: v3".
>
> /etc/mtab is linked to /proc/mounts.
That's not really a supported configuration, AFAIK. While /etc/mtab
and /proc/mounts are obviously similar, they're not identical, and
you've run into one of the results.
That said, I really can't fathom why mount wants "vers=3" but refuses
to accept "v3", while the kernel only reports "v3". It seems like a
pointless inconsistency. Why not have mount accept "v2", "v3", and
"v4" as synoyms for the corresponding "vers=" values?
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-07-29 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 6:36 remount error: 'unknown nfs mount option: v3' Nitin Chandrachoodan
2003-07-29 22:06 ` Chip Salzenberg [this message]
2003-07-29 22:28 ` Trond Myklebust
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=20030729220602.GA18733@perlsupport.com \
--to=chip@pobox.com \
--cc=nfs@lists.sourceforge.net \
--cc=nitin@tenet.res.in \
/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 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.