From: "Wim Colgate" Subject: different mounts to the same server export Date: Thu, 4 Oct 2007 14:24:33 -0700 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1066376869==" To: Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1IdYBc-0006nA-1k for nfs@lists.sourceforge.net; Thu, 04 Oct 2007 14:24:48 -0700 Received: from webmailrdm.xensource.com ([66.228.214.202]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1IdYBf-0004ry-S0 for nfs@lists.sourceforge.net; Thu, 04 Oct 2007 14:24:53 -0700 List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net This is a multi-part message in MIME format. --===============1066376869== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C806CC.FFBBF242" This is a multi-part message in MIME format. ------_=_NextPart_001_01C806CC.FFBBF242 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a question/issue relating to different mounts to the same server export with different attributes.=20 =20 My client is an Ubuntu distro (Linux wimc 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux) =20 Suppose from the same linux client I want to have two different accesses of the same export, but with different attributes. For example: =20 $ mount rdmx2:/public /mnt/public -o hard,rw =20 and =20 $ mount rdmx2:/public /mnt/scratch -o soft,ro =20 And also: =20 # mount rdmx2:/public/wim /mnt/wim -o soft,ro =20 Obviously, depending on which path I take to get at the underlying files (/mnt/public vs. /mnt/scratch) I'd expect the attributes to be honored and the behavior as specified. =20 However, what I'm seeing is that this is not the case. Dumping information with the mount command shows the attributes as specified. But cat'ing /proc/mounts shows the first attributes for all mounts.=20 =20 $mount=20 rdmx2:/public on /mnt/public type nfs (rw,addr=3D172.24.0.71) rdmx2:/public on /mnt/scratch type nfs (ro,soft,addr=3D172.24.0.71) rdmx2:/public/wim on /mnt/wim type nfs (ro,soft,addr=3D172.24.0.71) =20 $ cat /proc/mounts rdmx2:/public /mnt/public nfs rw,vers=3D3,rsize=3D32768,wsize=3D32768,hard,intr,proto=3Dtcp,timeo=3D600= ,retrans=3D 2,sec=3Dsys,addr=3Drdmx2 0 0 rdmx2:/public /mnt/scratch nfs rw,vers=3D3,rsize=3D32768,wsize=3D32768,hard,intr,proto=3Dtcp,timeo=3D600= ,retrans=3D 2,sec=3Dsys,addr=3Drdmx2 0 0 rdmx2:/public/wim /mnt/wim nfs rw,vers=3D3,rsize=3D32768,wsize=3D32768,hard,intr,proto=3Dtcp,timeo=3D600= ,retrans=3D 2,sec=3Dsys,addr=3Drdmx2 0 0 =20 and even though mounted as a read-only file system I can create a file on it..: =20 $ echo junk > /mnt/wim/foo $ cat /mnt/wim/foo junk $ =20 Is there a known issue/problem or is this as designed? =20 Thanks, =20 Wim ------_=_NextPart_001_01C806CC.FFBBF242 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have a question/issue relating to different mounts = to the same server export with different attributes. =

My client is an Ubuntu distro (Linux wimc = 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 = GNU/Linux)

Suppose from the same linux client I want to have two = different accesses of the same export, but with different attributes. For = example:

$ mount rdmx2:/public /mnt/public –o = hard,rw

and

$ mount rdmx2:/public /mnt/scratch –o = soft,ro

And also:

# mount rdmx2:/public/wim /mnt/wim –o = soft,ro

Obviously, depending on which path I take to get at = the underlying files (/mnt/public vs. /mnt/scratch) I’d expect the = attributes to be honored and the behavior as = specified.

However, what I’m seeing is that this is not = the case. Dumping information with the mount command shows the attributes as = specified. But cat’ing /proc/mounts shows the first attributes for all mounts. =

$mount

rdmx2:/public on /mnt/public type nfs = (rw,addr=3D172.24.0.71)

rdmx2:/public on /mnt/scratch type nfs (ro,soft,addr=3D172.24.0.71)

rdmx2:/public/wim on /mnt/wim type nfs (ro,soft,addr=3D172.24.0.71)

$ cat /proc/mounts

rdmx2:/public /mnt/public nfs rw,vers=3D3,rsize=3D32768,wsize=3D32768,hard,intr,proto=3Dtcp,timeo=3D600= ,retrans=3D2,sec=3Dsys,addr=3Drdmx2 0 0

rdmx2:/public /mnt/scratch nfs rw,vers=3D3,rsize=3D32768,wsize=3D32768,hard,intr,proto=3Dtcp,timeo=3D600= ,retrans=3D2,sec=3Dsys,addr=3Drdmx2 0 0

rdmx2:/public/wim /mnt/wim nfs rw,vers=3D3,rsize=3D32768,wsize=3D32768,hard,intr,proto=3Dtcp,timeo=3D600= ,retrans=3D2,sec=3Dsys,addr=3Drdmx2 0 0

and even though mounted as a read-only file system I = can create a file on it..:

$ echo junk > = /mnt/wim/foo

$ cat /mnt/wim/foo

junk

$

Is there a known issue/problem or is this as = designed?

Thanks,

Wim

------_=_NextPart_001_01C806CC.FFBBF242-- --===============1066376869== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ --===============1066376869== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs --===============1066376869==--