All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Schrier <wschrier@neolinear.com>
To: Eff Norwood <enorwood@effrem.com>
Cc: nfs@lists.sourceforge.net, it@neolinear.com
Subject: Re: NFS Locking Issue - Solaris-Linux
Date: Tue, 22 Oct 2002 11:21:23 -0400	[thread overview]
Message-ID: <3DB56CF3.29848F2F@neolinear.com> (raw)
In-Reply-To: CFEAJJEGMGECBCJFLGDBMECLCGAA.enorwood@effrem.com

> -Are you using automounter

Yes

> -Are you using NIS (if yes what kind of machine is the master)

No, we are using NIS+ though.  The master and replica servers are both Sparc
Solaris - the master is Solaris 2.6, the replica is Solaris 8.

> -What are your mount options

The corresponding line from our auto_direct table follows:
/zone           -actimeo=0,vers=2       raidzone:/home

The /etc/exports file on the raidzone box looks as follows:
/home   192.9.200.0/255.255.255.0(rw,no_root_squash,insecure,no_auth_nlm)
10.5.0.0/255.255.255.0(rw,insecure,no_
auth_nlm) 10.3.0.0/255.255.255.0(rw,insecure,no_auth_nlm)


> -What's the version of RedHat that works

I don't think I follow you here... Do you mean which Redhat version on the
Raidzone box?  If so, I believe that Raidzone would have been testing with
their most recent kernel version - which is what we are also running.  If you
mean as a client, I believe any version of RedHat is able to successfully lock
files.

> -Solaris Sparc or Solaris Intel

This is all on Solaris Sparc.

> Finally, will the Redhat box as a client lock the Raidzone or is it just the
> Solaris machines?

Yes - files shared from the Raidzone box are able to be locked from
HPUX machines, and other Linux boxes (both Redhat and Debian) on the network.
It is just the Solaris machines that are unable to lock files.

Thanks for the help!  If I can provide any further information, please don't
hesitate to ask.

Bill

--
William J. Schrier              Phone: 412.968.5780 x151
Neolinear, Inc.                 Fax:   412.968.5788
583 Epsilon Drive               Email: wschrier@neolinear.com
Pittsburgh, PA  15238





-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-10-22 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 14:08 NFS Locking Issue - Solaris-Linux Bill Schrier
2002-10-22 14:52 ` Eff Norwood
2002-10-22 15:21   ` Bill Schrier [this message]
2002-10-23 16:21     ` Scott McDermott
2002-10-22 16:02 ` Daniel Forrest
2002-10-23 18:52   ` Bill Schrier
2002-10-25 17:53     ` Daniel Forrest
2002-10-28 14:25       ` Bill Schrier

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=3DB56CF3.29848F2F@neolinear.com \
    --to=wschrier@neolinear.com \
    --cc=enorwood@effrem.com \
    --cc=it@neolinear.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.