Linux NFS development
 help / color / mirror / Atom feed
From: Michael Walker <Michael.Walker@Cassatt.COM>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net, mwalker@cassatt.com
Subject: Re: NFS mounts being mounted read-only depending upon mount order???
Date: Mon, 20 Nov 2006 14:00:47 -0800	[thread overview]
Message-ID: <4562258F.9040605@Cassatt.COM> (raw)
In-Reply-To: <1164059027.5723.77.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> On Mon, 2006-11-20 at 13:22 -0800, Michael Walker wrote:
> 
> There _are_ workarounds available. You can use the 'fsid' export option
> to tell knfsd to export the directories as if they were different
> filesystems.
> 
> For instance if I have
> 
>         /export/home	 141.211.133.0/24(rw,sync,no_subtree_check,fsid=0)
>         /export/home/trondmy 141.211.133.0/24(rw,sync,no_subtree_check,fsid=3)
> 
> in /etc/exports on the server, then I can do
> 
> mount -t nfs -oro server:/export/home /mnt/foo
> mount -t nfs -orw server:/export/home/trondmy /mnt/bar
> 
> with no trouble. From 'cat /proc/mounts'
> 
> server:/export/home /mnt/foo nfs rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=server 0 0
> server:/export/home/trondmy /mnt/bar nfs ro,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=server 0 0
> 
> as expected.

Oh - promising.

So - would I need to make the fsid unique for each mount - or could I just divide
them into two pools.  'fsid=1' for all 'read-only' exported filesystems
and 'fsid=2' for all read-write exported filesystems?

We could possibly make something like this work.

I could possibly generate unique fsid's for each export - but if the
above simple logic would be sufficient - that would be easiest.


> 
>> Can you point me to where the required 'mount --bind' fixes are
>> being discussed?  I haven't been able to find the
>> thread in the 'lkml' (not that it isn't there somewhere).
>>
>> Without the matching 'mount --bind' fixes this is a very serious
>> regression for us?
> 
> I believe the most recent patchsets can be found from
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=115447687730218&w=2
> 

Thanx for the pointer - I'll track this thread down....


_Mike_


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2006-11-20 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 18:22 NFS mounts being mounted read-only depending upon mount order??? Michael Walker
2006-11-20 20:57 ` Michael Walker
2006-11-20 21:10   ` Trond Myklebust
2006-11-20 21:22     ` Michael Walker
2006-11-20 21:43       ` Trond Myklebust
2006-11-20 22:00         ` Michael Walker [this message]

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=4562258F.9040605@Cassatt.COM \
    --to=michael.walker@cassatt.com \
    --cc=mwalker@cassatt.com \
    --cc=nfs@lists.sourceforge.net \
    --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