From: Peter Staubach <staubach@redhat.com>
To: Chris Carlson <c.carlson@aristoslogic.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS won't mount rw
Date: Mon, 24 Sep 2007 10:00:28 -0400 [thread overview]
Message-ID: <46F7C2FC.1010908@redhat.com> (raw)
In-Reply-To: <46F460D9.1000105@aristoslogic.com>
Chris Carlson wrote:
> We have a new problem that I was hoping someone could help with.
>
> We have a Snap Appliance NFS server. It has been recently upgraded, so
> it should have good NFS server software on it (though this isn't a
> guarantee).
>
> We have a couple dozen Linux 2.4 systems that have it mounted (via
> automount). No problem. All mount is with root_squash and rw (not sure
> of the other options).
>
> We just tried to "automount" it to a RedHat Linux Enterprise 5 system,
> and it mounted fine - except it is read-only. Why would Linux 2.6 not
> mount it rw like the other systems? Is it some security thing that we
> don't know? Is there a bug in the NFS client on RH Linux?
>
> If anybody knows what we're missing, I'd appreciate a clue.
I don't suppose that this file system from the server is already
mounted somewhere on the client and is mounted there read-only?
The current RHEL-5 has a problem doing this. It should be fixed
in the next release of RHEL-5.
Thanx...
ps
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-09-24 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 0:24 NFS won't mount rw Chris Carlson
2007-09-24 14:00 ` Peter Staubach [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=46F7C2FC.1010908@redhat.com \
--to=staubach@redhat.com \
--cc=c.carlson@aristoslogic.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.