From: "Gregory Baker" <gregory.baker@amd.com>
To: gregory.baker@amd.com
Cc: julia bauer <julia.bauer@amd.com>,
nfs@lists.sourceforge.net,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: inconsistent mount attributes (ro/rw), RHEL5 / Netapp
Date: Mon, 23 Apr 2007 13:36:02 -0500 [thread overview]
Message-ID: <462CFC92.2080201@amd.com> (raw)
In-Reply-To: <4627EBFC.2090704@amd.com>
...closing the loop on what we've found out... it doesn't appear that a
convenient workaround (at the mount level) exists. We'll play around
with local executable automount maps to see if that will work for us.
Thanks,
--Greg
*****
Indeed, now that I read that comment by Trond and went to the source
code, I found out about upstream commit
54ceac4515986030c2502960be620198dd8fe25b.
The idea is that having a single super_block structure per server per
FSID prevents corner cases that can lead to corrupt dentry cache trees,
prevents conflicting buffer cache contents to what ends up being the
same file, and some other scary situations.
So the deal is, the mount flags (and NFS options) are set only the first
time that a given combination of server and filesystem are mounted. If
you ever mount the same filesystem from the same server on another
mountpoint, you'll get the flags and options that were passed on to the
first mount. There's no working around that.
*****
Gregory Baker wrote:
> Trond Myklebust wrote:
> > On Thu, 2007-04-19 at 15:37 -0500, Gregory Baker wrote:
> >
> >> ---+ BAD RHEL 5 64 system
> > ...
> >> [root@adcgar04 mnt2]# cat /proc/mounts | grep mnt2
> >> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs
> >>
> ro,vers=3,rsize=65536,wsize=65536,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=eng
>
> >> 0 0
> >
> > That would be your problem right there. Is the same volume perhaps
> > mounted read-only somewhere else on the same client? That is no longer
> > allowed.
> >
> > Cheers
> > Trond
> >
>
> Ah, news to me!
>
> So if you mount a volume ro at one mount point /mnt1 and then try to
> mount the same volume rw at a second mount point /mnt2 you'll run into
> problems? Apologies, didn't catch this in release notes. Thanks!
>
> --Greg
>
> ---+ A New Beginning
>
> [root@adcgar04 /]# umount -a -t nfs
>
> [root@adcgar04 /]# mount -v | grep pandora
>
> [root@adcgar04 /]# cat /proc/mounts | grep pandora
>
> [root@adcgar04 /]# mount eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2
>
> [root@adcgar04 /]# mount -v | grep pandora
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs
> (rw,addr=163.181.34.137)
>
> [root@adcgar04 /]# cat /proc/mounts | grep pandora
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs
> rw,vers=3,rsize=65536,wsize=65536,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=eng
> 0 0
>
> [root@adcgar04 /]# touch /mnt2/asdf
>
> ---+ The ro Strikes Back
>
> [root@adcgar04 /]# mount -o ro
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt1
>
> [root@adcgar04 /]# mount -o rw
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2
>
> [root@adcgar04 /]# mount -v | grep mnt
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt1 type nfs
> (ro,addr=163.181.34.137)
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs
> (rw,addr=163.181.34.137)
>
> [root@adcgar04 /]# cat /proc/mounts | grep mnt
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt1 nfs
> ro,vers=3,rsize=65536,wsize=65536,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=eng
> 0 0
> eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs
> ro,vers=3,rsize=65536,wsize=65536,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=eng
> 0 0
>
> [root@adcgar04 /]# touch /mnt2/asdf
> touch: cannot touch `/mnt2/asdf': Read-only file system
>
>
>
>
>
--
----------------------------------------------------------------------
Greg Baker 512-602-3287 (work)
gregory.baker@amd.com 512-602-6970 (fax)
5204 E. Ben White Blvd MS 625 512-555-1212 (info)
Austin, TX 78741
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-23 18:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 21:53 inconsistent mount attributes (ro/rw), RHEL5 / Netapp Gregory Baker
[not found] ` <1176948355.6422.72.camel@heimdal.trondhjem.org>
2007-04-19 18:24 ` Gregory Baker
2007-04-19 18:31 ` Trond Myklebust
2007-04-19 20:37 ` Gregory Baker
2007-04-19 22:11 ` Trond Myklebust
2007-04-19 22:23 ` Gregory Baker
2007-04-23 18:36 ` Gregory Baker [this message]
2007-04-24 19:57 ` Gregory Baker
2007-04-24 22:01 ` Gregory Baker
2007-05-04 20:30 ` Gregory Baker
2007-05-04 21:41 ` Trond Myklebust
2007-05-05 15:37 ` Ian Kent
2007-05-05 17:17 ` Trond Myklebust
2007-05-05 18:27 ` Ian Kent
2007-05-05 18:49 ` Trond Myklebust
2007-05-06 4:51 ` Ian Kent
2007-05-14 13:17 ` Karel Zak
2007-05-14 13:24 ` Trond Myklebust
2007-05-14 14:39 ` Ian Kent
2007-05-14 15:47 ` Trond Myklebust
2007-05-14 15:56 ` Paul Krizak
2007-05-14 16:06 ` Trond Myklebust
2007-05-14 16:06 ` Ian Kent
2007-05-14 22:41 ` Neil Brown
2007-05-14 23:11 ` Trond Myklebust
2007-05-14 23:58 ` Neil Brown
2007-05-16 0:27 ` Trond Myklebust
2007-05-16 1:36 ` [PATCH 1/2] NFS: Add the mount option nosharedcache Trond Myklebust
2007-05-16 3:46 ` Neil Brown
2007-05-16 13:22 ` Trond Myklebust
2007-05-17 2:13 ` [PATCH 1/2] NFS: Add the mount option "nosharecache" Trond Myklebust
2007-05-18 3:12 ` Ian Kent
2007-05-18 13:20 ` Trond Myklebust
2007-05-18 14:57 ` Ian Kent
2007-05-17 2:13 ` [PATCH] mount.nfs: Add support for the 'nosharecache' option Trond Myklebust
2007-05-17 2:13 ` [PATCH 2/2] NFS: Error when mounting the same filesystem with different options Trond Myklebust
2007-05-29 2:35 ` Neil Brown
2007-06-05 23:49 ` Trond Myklebust
2007-05-16 1:37 ` Trond Myklebust
2007-05-15 13:58 ` inconsistent mount attributes (ro/rw), RHEL5 / Netapp Chuck Lever
2007-05-15 14:33 ` Trond Myklebust
2007-05-15 16:57 ` Gregory Baker
2007-05-14 14:30 ` Ian Kent
2007-05-14 13:03 ` Karel Zak
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=462CFC92.2080201@amd.com \
--to=gregory.baker@amd.com \
--cc=Trond.Myklebust@netapp.com \
--cc=julia.bauer@amd.com \
--cc=nfs@lists.sourceforge.net \
/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.