public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michel Lespinasse <walken@zoy.org>
To: linux-kernel@vger.kernel.org
Cc: trond.myklebust@fys.uio.no
Subject: nfsroot and locking
Date: Mon, 4 Jun 2007 00:23:40 -0700	[thread overview]
Message-ID: <20070604072340.GC3315@zoy.org> (raw)

Hi,

I have a quick question about nfsroot in linux: Is there any way to
use nfsv3 in the nfsroot (nolock is OK there), and then mount other
directories with locking enabled ?

The default nfs options when using nfsroot are to use nfsv2 without locking.
After booting, one can mount other filesystems which will default to
nfsv3 with locking.

By passing extra options in the nfsroot parameter, one can boot with nfs3
if desired. For example v3,tcp,rsize=131072,wsize=131072,intr set the
same options in nfsroot than would otherwise be the after-boot default,
except that locking stays disabled (I understand lockd can not be started
as portmap is not running during boot).

However after starting the nfsroot with nfsv3, I am unable to mount any
other shares with locking. Passing the 'lock' option to mount will add
'lock' in /etc/mtab, but /proc/mounts will still show the share with 'nolock'
and rpcinfo shows that lockd was not started.

Is there a reason for this, or an easy workaround ?

for reference, I'm currently running debian etch with a 2.6.20.12 kernel.
Also I'd appreciate to be copied on replies as I'm not on the list.

Thanks,

-- 
Michel "Walken" Lespinasse
"Bill Gates is a monocle and a Persian cat away from being the villain
in a James Bond movie." -- Dennis Miller

                 reply	other threads:[~2007-06-04  7:46 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=20070604072340.GC3315@zoy.org \
    --to=walken@zoy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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