From: Stephen Carville <stephen@totalflood.com>
To: NFS List <nfs@lists.sourceforge.net>
Subject: Re: NFS3 in RHEL3
Date: Fri, 14 Apr 2006 14:20:31 -0700 [thread overview]
Message-ID: <4440121F.5020704@totalflood.com> (raw)
In-Reply-To: <443F37FA.2060402@oracle.com>
shashi wrote:
> Hi
>
> A small doubt about NFS3 in Linux . If i mount a NFS share (From NetApp
> , ONTAP 6.5 ) on a Linux machine with only ro,nolock options , then
> still the NFS mount options like
> bg,intr,hard,timeo,wsize,rsize,nfsvers,tcp are still applied ? If they
> are applied , how can i check is those are applied or not ?
>
> In my Linux box , after mounting with only ro,nolock options .....
>
> [root@<hostname>]# mount | grep < Mount point>
> <NFS server> on < Mount point > type nfs (ro,nolock,addr=144.20.129.248)
>
> In this case , is other other options like
> bg,intr,hard,timeo,wsize,rsize,nfsvers,tcp are applied ? if they are
> applied , what are the default values ?
>
> Please answer to my question.
>
"man nfs" lists the options and their defaults
--
Stephen Carville <stephen@totalflood.com>
Unix and Network Admin
Nationwide Totalflood
6033 W. Century Blvd
Los Angeles, CA 90045
310-342-3602
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-04-14 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 5:49 NFS3 in RHEL3 shashi
2006-04-14 14:54 ` Chuck Lever
2006-04-14 21:20 ` Stephen Carville [this message]
2006-04-14 22:12 ` Chuck Lever
2006-04-14 23:38 ` Garrick Staples
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=4440121F.5020704@totalflood.com \
--to=stephen@totalflood.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.