machine can't mount to itself
in [Solaris]
|
From: Casper H.S. Dik on 5 Apr 2010 06:04 wbe(a)ubeblock.psr.com.invalid (Winston) writes: >Stefaan A Eeckels wrote: >>> As far as I remember, we had automounted home directories in the days >>> of SunOS 4.x, which had no such thing as lofs, >v_borchert(a)despammed.com (Volker Borchert) replied: >> 4.1.4 does. >I found a man page for lofs(4S) that said: >"Sun Release 4.1 Last change: 18 May 1989" SunOS 4.x had lofs, automount and the translucent filesystem. Casper -- Expressed in this posting are my opinions. They are in no way related to opinions held by my employer, Sun Microsystems. Statements on Sun products included here are not gospel and may be fiction rather than truth.
From: Stefaan A Eeckels on 5 Apr 2010 09:41 On 05 Apr 2010 10:04:04 GMT Casper H.S. Dik <Casper.Dik(a)Sun.COM> wrote: > SunOS 4.x had lofs, automount and the translucent filesystem. Just as a matter of interest, did automount already transparently use lofs for local mounts in SunOS 4.x? Is it really possible to wedge Solaris by automounting an NFS file system on the same system that exports it? -- Stefaan A Eeckels -- "The most common of all follies is to believe passionately in the palpably not true. It is the chief occupation of mankind." --H. L. Mencken
From: Casper H.S. Dik on 5 Apr 2010 13:54 Stefaan A Eeckels <hoendech(a)ecc.lu> writes: >On 05 Apr 2010 10:04:04 GMT >Casper H.S. Dik <Casper.Dik(a)Sun.COM> wrote: >> SunOS 4.x had lofs, automount and the translucent filesystem. >Just as a matter of interest, did automount already transparently use >lofs for local mounts in SunOS 4.x? I'm not sure it did; it seems to be using a /tmp_mnt hierarchy and not the "use lofs". >Is it really possible to wedge Solaris by automounting an NFS file >system on the same system that exports it? You can't easily do it (autofs won't do it); there used to be an issue with UFS & NFS. I think it may have been fixed. Casper -- Expressed in this posting are my opinions. They are in no way related to opinions held by my employer, Sun Microsystems. Statements on Sun products included here are not gospel and may be fiction rather than truth.
From: Darren Dunham on 5 Apr 2010 20:13
On Apr 2, 2:33 pm, ITguy <southa...(a)gmail.com> wrote: > > >jgs# share -F nfs -o ro=jgs.arlut.utexas.edu,anon=0 /VOLUMES/space > > > Just a WAG, how about share -o ro=jgs or share -o ro=localhost ? > > Guessing name lookup issue. > > To rule out the possibility of a name service error: > # share -F nfs -o ro=<IP_Address>,anon=0 /VOLUMES/space <IP_Address> is not a valid entry in an access list. You can get close to it by doing a network specification with a 32-bit subnet mask, though. But you have to stick the /32 on the end. > To resolve the name resolution issue: On the NFS server, use the > command "getent hosts <client_IP>" and ensure that the first returned > result is the one present in the netgroup. Absolutely. -- Darren |