From: "Gregory Baker" <gregory.baker@amd.com>
To: "Trond Myklebust" <Trond.Myklebust@netapp.com>
Cc: julia bauer <julia.bauer@amd.com>, nfs@lists.sourceforge.net
Subject: Re: inconsistent mount attributes (ro/rw), RHEL5 / Netapp
Date: Thu, 19 Apr 2007 15:37:23 -0500 [thread overview]
Message-ID: <4627D303.8060009@amd.com> (raw)
In-Reply-To: <1177007479.6623.14.camel@heimdal.trondhjem.org>
Myklebust wrote:
> On Thu, 2007-04-19 at 13:24 -0500, Gregory Baker wrote:
>
>> Ideas?
>
> Perhaps a limitation on the number of entries in the netgroup on the
> server?
>
> Cheers
> Trond
I've seen past Netapp/netgroups non-happiness. In this case the
netgroup is relatively small... I tested quickly by moving the rhel5
system (adcgar04) to the top of the netgroup list with no affect.
[greg@apathy greg]$ show_netgroup volexport-pandora
adcgar04.amd.com <-------RHEL 5 64 system
nextimon.amd.com
i-sif1.amd.com
apathy.amd.com
build-lipc2.amd.com
build-el3-32.amd.com
build-el3-64.amd.com <------RHEL 3 64 system
build-el5-32.amd.com
build-el5-64.amd.com
build-sl10-32.amd.com
build-sl10-64.amd.com
hummus01.amd.com
loriol.amd.com
coolhand.amd.com
orkney.amd.com
purgatory.amd.com
reverse.amd.com
sideways.amd.com
testpig3.amd.cfffffadfm
texas2s20.amd.com
xhaust.amd.comrond
---+What the filer thinks
[greg@apathy greg]$ sudo rsh eng exportfs -c 163.181.61.69
/vol/vol4/pandora/pandora-k26_g25_64-2 root
exportfs: 163.181.61.69 has root access to /vol/vol4/pandora
[greg@apathy greg]$ sudo rsh eng exportfs -c 163.181.61.69
/vol/vol4/pandora/pandora-k26_g25_64-2 rw
exportfs: 163.181.61.69 has rw access to /vol/vol4/pandora
[greg@apathy greg]$ host 163.181.61.69
69.61.181.163.in-addr.arpa domain name pointer adcgar04.amd.com.
---+ BAD RHEL 5 64 system
[root@adcgar04 /]# mount eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2
[root@adcgar04 mnt2]# mount -v | grep mnt2
eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs
(rw,addr=163.181.34.137)
[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
[root@adcgar04 mnt2]# touch asdf
touch: cannot touch `asdf': Read-only file system
---+GOOD RHEL 3 64 system
[root@build-el3-64 root]# mount -o tcp
eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2
[root@build-el3-64 root]# mount -v | grep mnt2
eng:/vol/vol4/pandora/pandora-k26_g25_64-2 on /mnt2 type nfs
(rw,tcp,addr=163.181.34.137)
[root@build-el3-64 root]# cat /proc/mounts | grep mnt2
eng:/vol/vol4/pandora/pandora-k26_g25_64-2 /mnt2 nfs
rw,v3,rsize=32768,wsize=32768,hard,tcp,lock,addr=eng 0 0
[root@build-el3-64 root]# cd /mnt2/
[root@build-el3-64 mnt2]# touch asdf
[root@build-el3-64 mnt2]# ls -la asdf
-rw-r--r-- 1 root root 0 Apr 19 15:35 asdf
--
----------------------------------------------------------------------
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-19 20: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 [this message]
2007-04-19 22:11 ` Trond Myklebust
2007-04-19 22:23 ` Gregory Baker
2007-04-23 18:36 ` Gregory Baker
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=4627D303.8060009@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox