From: Jim Rees <rees@umich.edu>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsroot mount options
Date: Thu, 2 Dec 2010 12:09:15 -0500 [thread overview]
Message-ID: <20101202170915.GB15530@merit.edu> (raw)
In-Reply-To: <11945697-DC88-4EB3-A9C8-F2A27E0E79BD@oracle.com>
Chuck Lever wrote:
On Dec 1, 2010, at 7:18 PM, Jim Rees wrote:
> If I boot diskless with nfsroot, why is the root file system mounted
> readonly? This makes sense for a file system on disk, since it may have to
> be checked before remounting rw, but I don't see why this is needed for
> nfsroot.
>
> Also, Documentation/filesystems/nfs/nfsroot.txt says that only nfs options
> can be given on the kernel nfsroot option, but I've seen a claim that you
> can also put "rw" here. Are other generic options possible? How about the
> nfs options that aren't listed in the doc? Should the doc be updated?
What kernel version are you looking at? I think 2.6.37-rc has some
nfsroot updates that allow all NFS options to be used.
Not sure about the generic mount options. Why not just try them and see?
This is Ubuntu lucid, so 2.6.32. I'm less concerned about the documentation
defect than the question about the default being readonly. Is there any
good reason other than to match the behavior of non-nfs root?
I ask because there has been a bug in ubuntu for a long time (a couple of
releases) that prevents nfsroot from working. Their mountall is broken and
can't remount an nfs root rw. They need to fix this obviously, but it got
me to wondering why the remount should be needed at all.
The bug report is here:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/537133
next prev parent reply other threads:[~2010-12-02 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 0:18 nfsroot mount options Jim Rees
2010-12-02 16:40 ` Chuck Lever
2010-12-02 17:09 ` Jim Rees [this message]
2010-12-02 18:11 ` Chuck Lever
2010-12-02 18:36 ` Jim Rees
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=20101202170915.GB15530@merit.edu \
--to=rees@umich.edu \
--cc=chuck.lever@oracle.com \
--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).