Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
Hi Tim, thanks, I'll look into that ... weirdly I get messages to the log file only the first time I try to access the drive, which is why I didn't get more information by putting the debug on ... however I made a mistake and will now need to wait for it to time-out (hopefully!) before checking again. Jon On Tue, 10 Dec 2019 at 22:55, Tim Mooney wrote: > In regard to: Re: [OpenIndiana-discuss] NFS Automount from FreeNAS > Server,...: > > > same issue, but with the latest versions of both OpenIndiana and FreeNAS > ... > > new hardware, on both counts: > > > > Dec 10 16:03:19 ascamrouter automountd[978]: [ID 784820 daemon.error] > > server ascamnfs01 not responding > > > > I can mount the filesystem manually, I can mount on Solaris 10, but I > can't > > use autofs. > > > > It doesn't appear to be any different if I'm using LDAP or not (I turned > > off LDAP for testing) ... > > > > does anyone have any idea where to start looking? > > I haven't used the automounter in ages, but this Oracle developer blog > post has a very interesting debug trick in it: > > https://blogs.oracle.com/cwb/debugging-automounter-problems > > Tim > > > On Mon, 23 Feb 2015 at 11:14, Jonathan Adams > wrote: > > > >> Hi, thanks for keeping on trying ... > >> > >> I was optimistic, till I discovered that our Infrastructure guy had put > >> comments on almost all the shares. > >> > >> Just for giggles I've added the snoop output from failed (snoopy.out) > and > >> working (snoopy2.out) in case that helps anyone. > >> > >> Jon > >> > >> On 20 February 2015 at 19:14, Till Wegmüller > wrote: > >> > >>> Hmm ok i've run out of ideas. > >>> > >>> It looks like a bug or a problematic Setting in FreeNAS. > >>> My Automount Works and can mount shares very reliably with /dev and > >>> /Hipster > >>> (newest 2015) > >>> Yours seems to work as well, atleast with solaris. > >>> > >>> Just for fun I had a little look around google to see if there are some > >>> fun > >>> FreeNAS Bugs. Was not disapointed http://vtricks.com/?p=2031 > >>> It Looks like FreeNas wants its shares to be commented :) > >>> > >>> Greetings Till > >>> > >>> > >>> On Friday 20 February 2015 16.15:05 Jonathan Adams wrote: > >>>> On 20 February 2015 at 15:56, Till Wegmüller > >>> wrote: > >>>>> no problem :) > >>>>> > >>>>> ... > >>>>> > >>>>> The No such file or directory Error Happens when automount can't find > >>> a > >>>>> directory on the Server and thus does not create and mount the > >>> Directory. > >>>> > >>>> jadams@jadlaptop:~$ dfshares mansalnfs01 > >>>> RESOURCE SERVER ACCESSTRANSPORT > >>>> mansalnfs01:/mnt/datapool mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/accountsmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/analystsmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/inorganics mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/organicsmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/technician mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/PM mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/bdmmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/qualitymansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/reception mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/IT mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/airmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/health mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/metals mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/sr mansalnfs01 - - > >>>> > >>>> in this case all the directories I'm trying to access are on > >>> datapool2/IT > >>>> ... it's a ZFS share. > >>>> > >>>>> My Question is from where does the truss output of the successful > >>>>> automount come from? > >>>> > >>>> ro
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
On Wed, Dec 11, 2019, 15:54 Tim Mooney wrote: > In regard to: Re: [OpenIndiana-discuss] NFS Automount from FreeNAS > Server,...: > > > As an OI newcomer, I'm somewhat confused. I thought mounting was done via > > /etc/vfstab entries? Or is something else/more being attempted here? > > There's a bit more going on here. > > vfstab entries for traditional filesystems are closer to the "static" end > of the filesystem mount "spectrum". Long before the days of an OS > automatically mounting a USB stick when you inserted it, the > autofs/automountd stack could do something kind of like that, but > generally aimed at network filesystems (NFS). > > The classic example that Sun used to champion was a cluster of diskless > workstations that auto-mounted NFS shares (like your home directory) > automatically when needed. automountd typically played a part in that. > > You can read more about it in > > https://en.wikipedia.org/wiki/Automounter > > and the OI/Solaris-ancestry bits in automount(1M), automountd(1M), > autofs(4). > > Tim > -- > Tim Mooney tim.moo...@ndsu.edu > Enterprise Computing & Infrastructure / > Division of Information Technology/701-231-1076 (Voice) > North Dakota State University, Fargo, ND 58105-5164 > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss Oh, I see. Thanks! > > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
In regard to: Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server,...: As an OI newcomer, I'm somewhat confused. I thought mounting was done via /etc/vfstab entries? Or is something else/more being attempted here? There's a bit more going on here. vfstab entries for traditional filesystems are closer to the "static" end of the filesystem mount "spectrum". Long before the days of an OS automatically mounting a USB stick when you inserted it, the autofs/automountd stack could do something kind of like that, but generally aimed at network filesystems (NFS). The classic example that Sun used to champion was a cluster of diskless workstations that auto-mounted NFS shares (like your home directory) automatically when needed. automountd typically played a part in that. You can read more about it in https://en.wikipedia.org/wiki/Automounter and the OI/Solaris-ancestry bits in automount(1M), automountd(1M), autofs(4). Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure / Division of Information Technology/701-231-1076 (Voice) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
On Tue, Dec 10, 2019 at 4:55 PM Tim Mooney wrote: > In regard to: Re: [OpenIndiana-discuss] NFS Automount from FreeNAS > Server,...: > > > same issue, but with the latest versions of both OpenIndiana and FreeNAS > ... > > new hardware, on both counts: > > > > Dec 10 16:03:19 ascamrouter automountd[978]: [ID 784820 daemon.error] > > server ascamnfs01 not responding > > > > I can mount the filesystem manually, I can mount on Solaris 10, but I > can't > > use autofs. > > > > It doesn't appear to be any different if I'm using LDAP or not (I turned > > off LDAP for testing) ... > > > > does anyone have any idea where to start looking? > > I haven't used the automounter in ages, but this Oracle developer blog > post has a very interesting debug trick in it: > > https://blogs.oracle.com/cwb/debugging-automounter-problems > > Tim > > > On Mon, 23 Feb 2015 at 11:14, Jonathan Adams > wrote: > > > >> Hi, thanks for keeping on trying ... > >> > >> I was optimistic, till I discovered that our Infrastructure guy had put > >> comments on almost all the shares. > >> > >> Just for giggles I've added the snoop output from failed (snoopy.out) > and > >> working (snoopy2.out) in case that helps anyone. > >> > >> Jon > >> > >> On 20 February 2015 at 19:14, Till Wegmüller > wrote: > >> > >>> Hmm ok i've run out of ideas. > >>> > >>> It looks like a bug or a problematic Setting in FreeNAS. > >>> My Automount Works and can mount shares very reliably with /dev and > >>> /Hipster > >>> (newest 2015) > >>> Yours seems to work as well, atleast with solaris. > >>> > >>> Just for fun I had a little look around google to see if there are some > >>> fun > >>> FreeNAS Bugs. Was not disapointed http://vtricks.com/?p=2031 > >>> It Looks like FreeNas wants its shares to be commented :) > >>> > >>> Greetings Till > >>> > >>> > >>> On Friday 20 February 2015 16.15:05 Jonathan Adams wrote: > >>>> On 20 February 2015 at 15:56, Till Wegmüller > >>> wrote: > >>>>> no problem :) > >>>>> > >>>>> ... > >>>>> > >>>>> The No such file or directory Error Happens when automount can't find > >>> a > >>>>> directory on the Server and thus does not create and mount the > >>> Directory. > >>>> > >>>> jadams@jadlaptop:~$ dfshares mansalnfs01 > >>>> RESOURCE SERVER ACCESSTRANSPORT > >>>> mansalnfs01:/mnt/datapool mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/accountsmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/analystsmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/inorganics mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/organicsmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool/technician mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/PM mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/bdmmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/qualitymansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool1/reception mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/IT mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/airmansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/health mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/metals mansalnfs01 - - > >>>> mansalnfs01:/mnt/datapool2/sr mansalnfs01 - - > >>>> > >>>> in this case all the directories I'm trying to access are on > >>> datapool2/IT > >>>> ... it's a ZFS share. > >>>> > >>>>> My Question is from where does the truss output of the successful > >>>>> automount come from? > >>>> > >>>> root@jadlaptop:~# ps -ef | grep automount > >>>> root 3599 3597 0 10:00:09 ? 0:00 > >>>> /usr/lib/autofs/automountd > >>>> root 3597 1 0 10:00:09 ? 0:00 > >>>> /usr/lib/autofs/automountd > >>
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
In regard to: Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server,...: same issue, but with the latest versions of both OpenIndiana and FreeNAS ... new hardware, on both counts: Dec 10 16:03:19 ascamrouter automountd[978]: [ID 784820 daemon.error] server ascamnfs01 not responding I can mount the filesystem manually, I can mount on Solaris 10, but I can't use autofs. It doesn't appear to be any different if I'm using LDAP or not (I turned off LDAP for testing) ... does anyone have any idea where to start looking? I haven't used the automounter in ages, but this Oracle developer blog post has a very interesting debug trick in it: https://blogs.oracle.com/cwb/debugging-automounter-problems Tim On Mon, 23 Feb 2015 at 11:14, Jonathan Adams wrote: Hi, thanks for keeping on trying ... I was optimistic, till I discovered that our Infrastructure guy had put comments on almost all the shares. Just for giggles I've added the snoop output from failed (snoopy.out) and working (snoopy2.out) in case that helps anyone. Jon On 20 February 2015 at 19:14, Till Wegmüller wrote: Hmm ok i've run out of ideas. It looks like a bug or a problematic Setting in FreeNAS. My Automount Works and can mount shares very reliably with /dev and /Hipster (newest 2015) Yours seems to work as well, atleast with solaris. Just for fun I had a little look around google to see if there are some fun FreeNAS Bugs. Was not disapointed http://vtricks.com/?p=2031 It Looks like FreeNas wants its shares to be commented :) Greetings Till On Friday 20 February 2015 16.15:05 Jonathan Adams wrote: On 20 February 2015 at 15:56, Till Wegmüller wrote: no problem :) ... The No such file or directory Error Happens when automount can't find a directory on the Server and thus does not create and mount the Directory. jadams@jadlaptop:~$ dfshares mansalnfs01 RESOURCE SERVER ACCESSTRANSPORT mansalnfs01:/mnt/datapool mansalnfs01 - - mansalnfs01:/mnt/datapool/accountsmansalnfs01 - - mansalnfs01:/mnt/datapool/analystsmansalnfs01 - - mansalnfs01:/mnt/datapool/inorganics mansalnfs01 - - mansalnfs01:/mnt/datapool/organicsmansalnfs01 - - mansalnfs01:/mnt/datapool/technician mansalnfs01 - - mansalnfs01:/mnt/datapool1/PM mansalnfs01 - - mansalnfs01:/mnt/datapool1/bdmmansalnfs01 - - mansalnfs01:/mnt/datapool1/qualitymansalnfs01 - - mansalnfs01:/mnt/datapool1/reception mansalnfs01 - - mansalnfs01:/mnt/datapool2/IT mansalnfs01 - - mansalnfs01:/mnt/datapool2/airmansalnfs01 - - mansalnfs01:/mnt/datapool2/health mansalnfs01 - - mansalnfs01:/mnt/datapool2/metals mansalnfs01 - - mansalnfs01:/mnt/datapool2/sr mansalnfs01 - - in this case all the directories I'm trying to access are on datapool2/IT ... it's a ZFS share. My Question is from where does the truss output of the successful automount come from? root@jadlaptop:~# ps -ef | grep automount root 3599 3597 0 10:00:09 ? 0:00 /usr/lib/autofs/automountd root 3597 1 0 10:00:09 ? 0:00 /usr/lib/autofs/automountd root 4441 4387 0 16:14:15 pts/16 0:00 grep automount root@jadlaptop:~# truss -f -p 3599 Is it from the same Computer as the failed one? Also are you running /hipster or /dev on this Computer? Hipster last updated 2015-01-15 (problems with Intel driver if I update at the moment) Other Tests you could do. What happens if you manually create the home? ? What happens if you replace the * and & in auto_home with some real usernames? no difference. What gets logged in syslog when Automount gets its config from LDAP? nothing. As I said, I can still access all the LDAP automounted shares from the Solaris 10 servers, and the Solaris 10 machines can access all the shares automounted from the FreeNAS box ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure / Division of Information Technology/701-231-1076 (Voice) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
Hi People, same issue, but with the latest versions of both OpenIndiana and FreeNAS ... new hardware, on both counts: Dec 10 16:03:19 ascamrouter automountd[978]: [ID 784820 daemon.error] server ascamnfs01 not responding I can mount the filesystem manually, I can mount on Solaris 10, but I can't use autofs. It doesn't appear to be any different if I'm using LDAP or not (I turned off LDAP for testing) ... does anyone have any idea where to start looking? Jon On Mon, 23 Feb 2015 at 11:14, Jonathan Adams wrote: > Hi, thanks for keeping on trying ... > > I was optimistic, till I discovered that our Infrastructure guy had put > comments on almost all the shares. > > Just for giggles I've added the snoop output from failed (snoopy.out) and > working (snoopy2.out) in case that helps anyone. > > Jon > > On 20 February 2015 at 19:14, Till Wegmüller wrote: > >> Hmm ok i've run out of ideas. >> >> It looks like a bug or a problematic Setting in FreeNAS. >> My Automount Works and can mount shares very reliably with /dev and >> /Hipster >> (newest 2015) >> Yours seems to work as well, atleast with solaris. >> >> Just for fun I had a little look around google to see if there are some >> fun >> FreeNAS Bugs. Was not disapointed http://vtricks.com/?p=2031 >> It Looks like FreeNas wants its shares to be commented :) >> >> Greetings Till >> >> >> On Friday 20 February 2015 16.15:05 Jonathan Adams wrote: >> > On 20 February 2015 at 15:56, Till Wegmüller >> wrote: >> > > no problem :) >> > > >> > > ... >> > > >> > > The No such file or directory Error Happens when automount can't find >> a >> > > directory on the Server and thus does not create and mount the >> Directory. >> > >> > jadams@jadlaptop:~$ dfshares mansalnfs01 >> > RESOURCE SERVER ACCESSTRANSPORT >> > mansalnfs01:/mnt/datapool mansalnfs01 - - >> > mansalnfs01:/mnt/datapool/accountsmansalnfs01 - - >> > mansalnfs01:/mnt/datapool/analystsmansalnfs01 - - >> > mansalnfs01:/mnt/datapool/inorganics mansalnfs01 - - >> > mansalnfs01:/mnt/datapool/organicsmansalnfs01 - - >> > mansalnfs01:/mnt/datapool/technician mansalnfs01 - - >> > mansalnfs01:/mnt/datapool1/PM mansalnfs01 - - >> > mansalnfs01:/mnt/datapool1/bdmmansalnfs01 - - >> > mansalnfs01:/mnt/datapool1/qualitymansalnfs01 - - >> > mansalnfs01:/mnt/datapool1/reception mansalnfs01 - - >> > mansalnfs01:/mnt/datapool2/IT mansalnfs01 - - >> > mansalnfs01:/mnt/datapool2/airmansalnfs01 - - >> > mansalnfs01:/mnt/datapool2/health mansalnfs01 - - >> > mansalnfs01:/mnt/datapool2/metals mansalnfs01 - - >> > mansalnfs01:/mnt/datapool2/sr mansalnfs01 - - >> > >> > in this case all the directories I'm trying to access are on >> datapool2/IT >> > ... it's a ZFS share. >> > >> > > My Question is from where does the truss output of the successful >> > > automount come from? >> > >> > root@jadlaptop:~# ps -ef | grep automount >> > root 3599 3597 0 10:00:09 ? 0:00 >> > /usr/lib/autofs/automountd >> > root 3597 1 0 10:00:09 ? 0:00 >> > /usr/lib/autofs/automountd >> > root 4441 4387 0 16:14:15 pts/16 0:00 grep automount >> > root@jadlaptop:~# truss -f -p 3599 >> > >> > Is it from the same Computer as the failed one? Also are you running >> > >> > > /hipster or /dev on this Computer? >> > >> > Hipster last updated 2015-01-15 (problems with Intel driver if I >> update at >> > the moment) >> > >> > > Other Tests you could do. >> > > What happens if you manually create the home? >> > >> > ? >> > >> > What happens if you replace the * and & in auto_home with some real >> > >> > > usernames? >> > >> > no difference. >> > >> > > What gets logged in syslog when Automount gets its config from LDAP? >> > >> > nothing. >> > >> > As I said, I can still access all the LDAP automounted shares from the >> > Solaris 10 servers, and the Solaris 10 machines can access all the >> shares >> > automounted from the FreeNAS box >> > ___ >> > openindiana-discuss mailing list >> > openindiana-discuss@openindiana.org >> > http://openindiana.org/mailman/listinfo/openindiana-discuss >> >> >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss >> > > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
Hi, thanks for keeping on trying ... I was optimistic, till I discovered that our Infrastructure guy had put comments on almost all the shares. Just for giggles I've added the snoop output from failed (snoopy.out) and working (snoopy2.out) in case that helps anyone. Jon On 20 February 2015 at 19:14, Till Wegmüller wrote: > Hmm ok i've run out of ideas. > > It looks like a bug or a problematic Setting in FreeNAS. > My Automount Works and can mount shares very reliably with /dev and > /Hipster > (newest 2015) > Yours seems to work as well, atleast with solaris. > > Just for fun I had a little look around google to see if there are some fun > FreeNAS Bugs. Was not disapointed http://vtricks.com/?p=2031 > It Looks like FreeNas wants its shares to be commented :) > > Greetings Till > > > On Friday 20 February 2015 16.15:05 Jonathan Adams wrote: > > On 20 February 2015 at 15:56, Till Wegmüller > wrote: > > > no problem :) > > > > > > ... > > > > > > The No such file or directory Error Happens when automount can't find a > > > directory on the Server and thus does not create and mount the > Directory. > > > > jadams@jadlaptop:~$ dfshares mansalnfs01 > > RESOURCE SERVER ACCESSTRANSPORT > > mansalnfs01:/mnt/datapool mansalnfs01 - - > > mansalnfs01:/mnt/datapool/accountsmansalnfs01 - - > > mansalnfs01:/mnt/datapool/analystsmansalnfs01 - - > > mansalnfs01:/mnt/datapool/inorganics mansalnfs01 - - > > mansalnfs01:/mnt/datapool/organicsmansalnfs01 - - > > mansalnfs01:/mnt/datapool/technician mansalnfs01 - - > > mansalnfs01:/mnt/datapool1/PM mansalnfs01 - - > > mansalnfs01:/mnt/datapool1/bdmmansalnfs01 - - > > mansalnfs01:/mnt/datapool1/qualitymansalnfs01 - - > > mansalnfs01:/mnt/datapool1/reception mansalnfs01 - - > > mansalnfs01:/mnt/datapool2/IT mansalnfs01 - - > > mansalnfs01:/mnt/datapool2/airmansalnfs01 - - > > mansalnfs01:/mnt/datapool2/health mansalnfs01 - - > > mansalnfs01:/mnt/datapool2/metals mansalnfs01 - - > > mansalnfs01:/mnt/datapool2/sr mansalnfs01 - - > > > > in this case all the directories I'm trying to access are on datapool2/IT > > ... it's a ZFS share. > > > > > My Question is from where does the truss output of the successful > > > automount come from? > > > > root@jadlaptop:~# ps -ef | grep automount > > root 3599 3597 0 10:00:09 ? 0:00 > > /usr/lib/autofs/automountd > > root 3597 1 0 10:00:09 ? 0:00 > > /usr/lib/autofs/automountd > > root 4441 4387 0 16:14:15 pts/16 0:00 grep automount > > root@jadlaptop:~# truss -f -p 3599 > > > > Is it from the same Computer as the failed one? Also are you running > > > > > /hipster or /dev on this Computer? > > > > Hipster last updated 2015-01-15 (problems with Intel driver if I update > at > > the moment) > > > > > Other Tests you could do. > > > What happens if you manually create the home? > > > > ? > > > > What happens if you replace the * and & in auto_home with some real > > > > > usernames? > > > > no difference. > > > > > What gets logged in syslog when Automount gets its config from LDAP? > > > > nothing. > > > > As I said, I can still access all the LDAP automounted shares from the > > Solaris 10 servers, and the Solaris 10 machines can access all the shares > > automounted from the FreeNAS box > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
Hmm ok i've run out of ideas. It looks like a bug or a problematic Setting in FreeNAS. My Automount Works and can mount shares very reliably with /dev and /Hipster (newest 2015) Yours seems to work as well, atleast with solaris. Just for fun I had a little look around google to see if there are some fun FreeNAS Bugs. Was not disapointed http://vtricks.com/?p=2031 It Looks like FreeNas wants its shares to be commented :) Greetings Till On Friday 20 February 2015 16.15:05 Jonathan Adams wrote: > On 20 February 2015 at 15:56, Till Wegmüller wrote: > > no problem :) > > > > ... > > > > The No such file or directory Error Happens when automount can't find a > > directory on the Server and thus does not create and mount the Directory. > > jadams@jadlaptop:~$ dfshares mansalnfs01 > RESOURCE SERVER ACCESSTRANSPORT > mansalnfs01:/mnt/datapool mansalnfs01 - - > mansalnfs01:/mnt/datapool/accountsmansalnfs01 - - > mansalnfs01:/mnt/datapool/analystsmansalnfs01 - - > mansalnfs01:/mnt/datapool/inorganics mansalnfs01 - - > mansalnfs01:/mnt/datapool/organicsmansalnfs01 - - > mansalnfs01:/mnt/datapool/technician mansalnfs01 - - > mansalnfs01:/mnt/datapool1/PM mansalnfs01 - - > mansalnfs01:/mnt/datapool1/bdmmansalnfs01 - - > mansalnfs01:/mnt/datapool1/qualitymansalnfs01 - - > mansalnfs01:/mnt/datapool1/reception mansalnfs01 - - > mansalnfs01:/mnt/datapool2/IT mansalnfs01 - - > mansalnfs01:/mnt/datapool2/airmansalnfs01 - - > mansalnfs01:/mnt/datapool2/health mansalnfs01 - - > mansalnfs01:/mnt/datapool2/metals mansalnfs01 - - > mansalnfs01:/mnt/datapool2/sr mansalnfs01 - - > > in this case all the directories I'm trying to access are on datapool2/IT > ... it's a ZFS share. > > > My Question is from where does the truss output of the successful > > automount come from? > > root@jadlaptop:~# ps -ef | grep automount > root 3599 3597 0 10:00:09 ? 0:00 > /usr/lib/autofs/automountd > root 3597 1 0 10:00:09 ? 0:00 > /usr/lib/autofs/automountd > root 4441 4387 0 16:14:15 pts/16 0:00 grep automount > root@jadlaptop:~# truss -f -p 3599 > > Is it from the same Computer as the failed one? Also are you running > > > /hipster or /dev on this Computer? > > Hipster last updated 2015-01-15 (problems with Intel driver if I update at > the moment) > > > Other Tests you could do. > > What happens if you manually create the home? > > ? > > What happens if you replace the * and & in auto_home with some real > > > usernames? > > no difference. > > > What gets logged in syslog when Automount gets its config from LDAP? > > nothing. > > As I said, I can still access all the LDAP automounted shares from the > Solaris 10 servers, and the Solaris 10 machines can access all the shares > automounted from the FreeNAS box > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
On 20 February 2015 at 15:56, Till Wegmüller wrote: > no problem :) > > ... > > The No such file or directory Error Happens when automount can't find a > directory on the Server and thus does not create and mount the Directory. > jadams@jadlaptop:~$ dfshares mansalnfs01 RESOURCE SERVER ACCESSTRANSPORT mansalnfs01:/mnt/datapool mansalnfs01 - - mansalnfs01:/mnt/datapool/accountsmansalnfs01 - - mansalnfs01:/mnt/datapool/analystsmansalnfs01 - - mansalnfs01:/mnt/datapool/inorganics mansalnfs01 - - mansalnfs01:/mnt/datapool/organicsmansalnfs01 - - mansalnfs01:/mnt/datapool/technician mansalnfs01 - - mansalnfs01:/mnt/datapool1/PM mansalnfs01 - - mansalnfs01:/mnt/datapool1/bdmmansalnfs01 - - mansalnfs01:/mnt/datapool1/qualitymansalnfs01 - - mansalnfs01:/mnt/datapool1/reception mansalnfs01 - - mansalnfs01:/mnt/datapool2/IT mansalnfs01 - - mansalnfs01:/mnt/datapool2/airmansalnfs01 - - mansalnfs01:/mnt/datapool2/health mansalnfs01 - - mansalnfs01:/mnt/datapool2/metals mansalnfs01 - - mansalnfs01:/mnt/datapool2/sr mansalnfs01 - - in this case all the directories I'm trying to access are on datapool2/IT ... it's a ZFS share. > My Question is from where does the truss output of the successful > automount come from? > root@jadlaptop:~# ps -ef | grep automount root 3599 3597 0 10:00:09 ? 0:00 /usr/lib/autofs/automountd root 3597 1 0 10:00:09 ? 0:00 /usr/lib/autofs/automountd root 4441 4387 0 16:14:15 pts/16 0:00 grep automount root@jadlaptop:~# truss -f -p 3599 Is it from the same Computer as the failed one? Also are you running > /hipster or /dev on this Computer? > Hipster last updated 2015-01-15 (problems with Intel driver if I update at the moment) > Other Tests you could do. > What happens if you manually create the home? > ? What happens if you replace the * and & in auto_home with some real > usernames? > no difference. > What gets logged in syslog when Automount gets its config from LDAP? > nothing. As I said, I can still access all the LDAP automounted shares from the Solaris 10 servers, and the Solaris 10 machines can access all the shares automounted from the FreeNAS box ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
no problem :) ... The No such file or directory Error Happens when automount can't find a directory on the Server and thus does not create and mount the Directory. My Question is from where does the truss output of the successful automount come from? Is it from the same Computer as the failed one? Also are you running /hipster or /dev on this Computer? Other Tests you could do. What happens if you manually create the home? What happens if you replace the * and & in auto_home with some real usernames? What gets logged in syslog when Automount gets its config from LDAP? Greetings Till Jonathan Adams schrieb am Friday 20 February 2015 10.05:42: > thanks for getting back to me :) > > ... > > now it says "no such file or directory" instead of "permission denied" ... > > setting the verbose logging in sharectl doesn't seem to produce much extra > output, nothing in syslog, and only a little extra in > /var/svc/log/system-filesystem-autofs:default.log (no error messages) > > Jon > > On 19 February 2015 at 20:03, Till Wegmüller wrote: > > > Looking at that truss output it seems that automount fails shortly after > > stat > > on the home directory without even contacting nfs. Could it be that > > automount > > has problems connecting to LDAP? > > > > I would like to see what happens if we disable LDAP for automounts. > > > > To do so Coment out all Lines starting with a plus '+' in /etc/auto_home > > and > > /etc/auto_master. > > > > Then Insert the following little Magic Line and reload automount > > * -fstype=nfs myserver:/myhomes/& > > Replace myserver and myhomes acordingly. > > > > This will instruct automount to search all the subdirectories of /home > > under > > myserver:/myhomes and mount hem if needed. > > > > If for example we have a user test and would do cd /home/test automount > > would > > map myserver:/myuser/test to /home/test automagically replacing & and * > > with > > test. > > > > If you now get a Permission denied error try to look in syslog, automount > > is > > very silent about failing to mount. > > To Increase automounts volume use: > > sharect set -p automountd_verbose=true autofs > > sharect set -p automount_verbose=true autofs > > > > Greetings Till > > > > On Thursday 19 February 2015 09.57:57 Jonathan Adams wrote: > > > via automount, it never gets mounted at all. > > > > > > hard mounted: > > > > > > root@jadlaptop:~# mount mansalnfs01:/mnt/datapool2/IT /mnt > > > root@jadlaptop:~# mount | grep mansalnfs01 > > > /mnt on mansalnfs01:/mnt/datapool2/IT > > > remote/read/write/setuid/devices/xattr/dev=9080001 on Thu Feb 19 09:49:24 > > > 2015 > > > > > > not sure if it helps, but attached is a section of via truss of the > > > automountd when accessing 2 different mount points from /home > > > > > > Jon > > > > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
thanks for getting back to me :)
...
now it says "no such file or directory" instead of "permission denied" ...
setting the verbose logging in sharectl doesn't seem to produce much extra
output, nothing in syslog, and only a little extra in
/var/svc/log/system-filesystem-autofs:default.log (no error messages)
Jon
On 19 February 2015 at 20:03, Till Wegmüller wrote:
> Looking at that truss output it seems that automount fails shortly after
> stat
> on the home directory without even contacting nfs. Could it be that
> automount
> has problems connecting to LDAP?
>
> I would like to see what happens if we disable LDAP for automounts.
>
> To do so Coment out all Lines starting with a plus '+' in /etc/auto_home
> and
> /etc/auto_master.
>
> Then Insert the following little Magic Line and reload automount
> * -fstype=nfs myserver:/myhomes/&
> Replace myserver and myhomes acordingly.
>
> This will instruct automount to search all the subdirectories of /home
> under
> myserver:/myhomes and mount hem if needed.
>
> If for example we have a user test and would do cd /home/test automount
> would
> map myserver:/myuser/test to /home/test automagically replacing & and *
> with
> test.
>
> If you now get a Permission denied error try to look in syslog, automount
> is
> very silent about failing to mount.
> To Increase automounts volume use:
> sharect set -p automountd_verbose=true autofs
> sharect set -p automount_verbose=true autofs
>
> Greetings Till
>
> On Thursday 19 February 2015 09.57:57 Jonathan Adams wrote:
> > via automount, it never gets mounted at all.
> >
> > hard mounted:
> >
> > root@jadlaptop:~# mount mansalnfs01:/mnt/datapool2/IT /mnt
> > root@jadlaptop:~# mount | grep mansalnfs01
> > /mnt on mansalnfs01:/mnt/datapool2/IT
> > remote/read/write/setuid/devices/xattr/dev=9080001 on Thu Feb 19 09:49:24
> > 2015
> >
> > not sure if it helps, but attached is a section of via truss of the
> > automountd when accessing 2 different mount points from /home
> >
> > Jon
> >
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
3313/4: door_return(0x08087970, 24, 0x, 0xFEA3EE00, 1007360) = 0
3313/4: time() = 1424426158
3313/4: open64("/etc/auto_home", O_RDONLY) = 10
3313/4: stat64("/etc/auto_home", 0xFEA3A298)= 0
3313/4: fstat64(10, 0xFEA3A034) = 0
3313/4: fstat64(10, 0xFEA39F34) = 0
3313/4: ioctl(10, TCGETA, 0xFEA39FF2) Err#25 ENOTTY
3313/4: read(10, " #\n # C o p y r i g h".., 1536)=
3313/4: llseek(10, 0xFFF4, SEEK_CUR)= 1099
3313/4: close(10) = 0
3313/4: door_return(0x08087970, 24, 0x, 0xFEA3EE00, 1007360) = 0
3313/4: time() = 1424426158
3313/4: open64("/etc/auto_home", O_RDONLY) = 10
3313/4: stat64("/etc/auto_home", 0xFEA39298)= 0
3313/4: fstat64(10, 0xFEA39034) = 0
3313/4: fstat64(10, 0xFEA38F34) = 0
3313/4: ioctl(10, TCGETA, 0xFEA38FF2) Err#25 ENOTTY
3313/4: read(10, " #\n # C o p y r i g h".., 1536)=
3313/4: llseek(10, 0xFFF4, SEEK_CUR)= 1099
3313/4: close(10) = 0
3313/4: open("/etc/svc/volatile/repository_door", O_RDONLY) = 10
3313/4: getpid()= 3313 [3311]
3313/4: door_call(10, 0xFEA3B1BC) = 0
3313/4: close(10) = 0
3313/4: fcntl(11, F_SETFD, 0x0001) = 0
3313/4: door_info(11, 0xFEA3B244) = 0
3313/4: getpid()= 3313 [3311]
3313/4: getpid()= 3313 [3311]
3313/4: door_call(11, 0xFEA3B17C) = 0
3313/4: getpid()= 3313 [3311]
3313/4: getpid()= 3313 [3311]
3313/4: door_call(11, 0xFEA3B17C) = 0
3313/4: getpid()= 3313 [3311]
3313/4: getpid()= 3313 [3311]
3313/4: door_call(11, 0xFEA3B17C) = 0
3313/4: getpid()= 3313 [3311]
3313/4: getpid()= 3313 [3311]
3313/4: door_call(11, 0xFEA3B17C) = 0
3313/4: getpid()
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
Looking at that truss output it seems that automount fails shortly after stat on the home directory without even contacting nfs. Could it be that automount has problems connecting to LDAP? I would like to see what happens if we disable LDAP for automounts. To do so Coment out all Lines starting with a plus '+' in /etc/auto_home and /etc/auto_master. Then Insert the following little Magic Line and reload automount * -fstype=nfs myserver:/myhomes/& Replace myserver and myhomes acordingly. This will instruct automount to search all the subdirectories of /home under myserver:/myhomes and mount hem if needed. If for example we have a user test and would do cd /home/test automount would map myserver:/myuser/test to /home/test automagically replacing & and * with test. If you now get a Permission denied error try to look in syslog, automount is very silent about failing to mount. To Increase automounts volume use: sharect set -p automountd_verbose=true autofs sharect set -p automount_verbose=true autofs Greetings Till On Thursday 19 February 2015 09.57:57 Jonathan Adams wrote: > via automount, it never gets mounted at all. > > hard mounted: > > root@jadlaptop:~# mount mansalnfs01:/mnt/datapool2/IT /mnt > root@jadlaptop:~# mount | grep mansalnfs01 > /mnt on mansalnfs01:/mnt/datapool2/IT > remote/read/write/setuid/devices/xattr/dev=9080001 on Thu Feb 19 09:49:24 > 2015 > > not sure if it helps, but attached is a section of via truss of the > automountd when accessing 2 different mount points from /home > > Jon > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
via automount, it never gets mounted at all. hard mounted: root@jadlaptop:~# mount mansalnfs01:/mnt/datapool2/IT /mnt root@jadlaptop:~# mount | grep mansalnfs01 /mnt on mansalnfs01:/mnt/datapool2/IT remote/read/write/setuid/devices/xattr/dev=9080001 on Thu Feb 19 09:49:24 2015 not sure if it helps, but attached is a section of via truss of the automountd when accessing 2 different mount points from /home Jon On 18 February 2015 at 19:11, Till Wegmüller wrote: > In That case OI will use its defaults. > OI Mounts per default as nfs4 so if you didnt specify -o vers=3 the shares > got > mounted as nfs4. > > Have a look at the output of the command mount in OI when the home is > automounted and when the home is mounted manually. > > mount shows you the options the nfsclient used to mount the share. > You can then try the options through to find the one that causes the error. > > Greetings Till > > On Wednesday 18 February 2015 14.00:17 Jonathan Adams wrote: > > no real options specified ... > > > > jadams@jadlaptop:~$ grep -v '^#' /etc/auto_master > > +auto_master > > /net-hosts-nosuid,nobrowse > > /homeauto_home-nobrowse > > > > jadams@jadlaptop:~$ more auto_master.ldif > > version: 1 > > DN: nisMapName=auto_master,dc=domain,dc=com > > objectClass: top > > objectClass: nisMap > > nisMapName: auto_master > > > > DN: cn=/net,nisMapName=auto_master,dc=domain,dc=com > > objectClass: nisObject > > cn: /net > > nismapentry: -hosts -nosuid,nobrowse > > nisMapName: auto_master > > > > DN: cn=/home,nisMapName=auto_master,dc=domain,dc=com > > objectClass: nisObject > > cn: /home > > nismapentry: auto_home -nobrowse > > nisMapName: auto_master > > > > (slightly sanitised, yes I know that "nisMap" is the deprecated version > of > > the automount stuff) > > > > the issue is with the automount, not with mounting in general ... I can > > hard mount it as root and access as my user with no trouble, I just can't > > access it via automount. > > > > The Linux laptops are usually running nfs v3, but only because we beat > them > > with sticks till they behave ... our Riverbeds cannot optimise nfs v4, > and > > permissions/ownership can go haywire when talking between Linux and > Solaris > > 10 as nfs v4. > > > > Jon > > > > > > On 18 February 2015 at 13:13, Predrag Zecevic [Unix Systems > Administrator] < > > predrag.zece...@2e-systems.com> wrote: > > > Hi, > > > > > > not sure if it is relevant, but in Solaris user home dirs were on > > > /export/home while /home was reserved for automounter. > > > > > > Not knowing FreeNAS (but some Linux systems), /home is location of user > > > home dirs. > > > Maybe problem solution can be looked in that direction? > > > > > > Regards. > > > > > > On 02/18/15 01:12 PM, Jonathan Adams wrote: > > >> I have an OpenIndiana laptop, it's running a copy of OpenLDAP as a > > >> replica > > >> of an OpenLDAP on our work server (syncs whenever it connects) ... > and it > > >> uses this OpenLDAP database to power it's automount. (not sure if > this is > > >> of any relevance, but included for completeness) > > >> > > >> I've been using this system for years in this configuration, but > recently > > >> some of our users had their home directories moved from a Solaris 10 > > >> server > > >> to a FreeNAS server. I noticed that I couldn't access their home > > >> directories using the automounted "/home" directory, it comes up > > >> "permission denied". I can however access the users home directory > if I > > >> hard mount as root. > > >> > > >> Our Solaris 10 servers have no trouble accessing the automounted > > >> directories, our Linux laptops have no issue either ... > > >> > > >> Does anyone else have issues like this, or know of any checks that I > can > > >> perform to see if I can find the fault? > > >> > > >> Ta > > >> > > >> Jon > > >> ___ > > >> openindiana-discuss mailing list > > >> openindiana-discuss@openindiana.org > > >> http://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > -- > > > Predrag Zečević > > > Technical Support Analyst > > > 2e Systems GmbH > > > > > > Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 > > > Mobile:+49 174 3109 288, Skype: predrag.zecevic > > > E-mail:predrag.zece...@2e-systems.com > > > > > > Headquarter: 2e Systems GmbH, Königsteiner Str. 87, > > > > > > 65812 Bad Soden am Taunus, Germany > > > > > > Company registration: Amtsgericht Königstein (Germany), HRB 7303 > > > Managing director:Phil Douglas > > > > > > http://www.2e-systems.com/ - Making your business fly! > > > > > > > > > ___ > > > openindiana-discuss mailing list > > > openindiana-discuss@openindiana.org > > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
In That case OI will use its defaults. OI Mounts per default as nfs4 so if you didnt specify -o vers=3 the shares got mounted as nfs4. Have a look at the output of the command mount in OI when the home is automounted and when the home is mounted manually. mount shows you the options the nfsclient used to mount the share. You can then try the options through to find the one that causes the error. Greetings Till On Wednesday 18 February 2015 14.00:17 Jonathan Adams wrote: > no real options specified ... > > jadams@jadlaptop:~$ grep -v '^#' /etc/auto_master > +auto_master > /net-hosts-nosuid,nobrowse > /homeauto_home-nobrowse > > jadams@jadlaptop:~$ more auto_master.ldif > version: 1 > DN: nisMapName=auto_master,dc=domain,dc=com > objectClass: top > objectClass: nisMap > nisMapName: auto_master > > DN: cn=/net,nisMapName=auto_master,dc=domain,dc=com > objectClass: nisObject > cn: /net > nismapentry: -hosts -nosuid,nobrowse > nisMapName: auto_master > > DN: cn=/home,nisMapName=auto_master,dc=domain,dc=com > objectClass: nisObject > cn: /home > nismapentry: auto_home -nobrowse > nisMapName: auto_master > > (slightly sanitised, yes I know that "nisMap" is the deprecated version of > the automount stuff) > > the issue is with the automount, not with mounting in general ... I can > hard mount it as root and access as my user with no trouble, I just can't > access it via automount. > > The Linux laptops are usually running nfs v3, but only because we beat them > with sticks till they behave ... our Riverbeds cannot optimise nfs v4, and > permissions/ownership can go haywire when talking between Linux and Solaris > 10 as nfs v4. > > Jon > > > On 18 February 2015 at 13:13, Predrag Zecevic [Unix Systems Administrator] < > predrag.zece...@2e-systems.com> wrote: > > Hi, > > > > not sure if it is relevant, but in Solaris user home dirs were on > > /export/home while /home was reserved for automounter. > > > > Not knowing FreeNAS (but some Linux systems), /home is location of user > > home dirs. > > Maybe problem solution can be looked in that direction? > > > > Regards. > > > > On 02/18/15 01:12 PM, Jonathan Adams wrote: > >> I have an OpenIndiana laptop, it's running a copy of OpenLDAP as a > >> replica > >> of an OpenLDAP on our work server (syncs whenever it connects) ... and it > >> uses this OpenLDAP database to power it's automount. (not sure if this is > >> of any relevance, but included for completeness) > >> > >> I've been using this system for years in this configuration, but recently > >> some of our users had their home directories moved from a Solaris 10 > >> server > >> to a FreeNAS server. I noticed that I couldn't access their home > >> directories using the automounted "/home" directory, it comes up > >> "permission denied". I can however access the users home directory if I > >> hard mount as root. > >> > >> Our Solaris 10 servers have no trouble accessing the automounted > >> directories, our Linux laptops have no issue either ... > >> > >> Does anyone else have issues like this, or know of any checks that I can > >> perform to see if I can find the fault? > >> > >> Ta > >> > >> Jon > >> ___ > >> openindiana-discuss mailing list > >> openindiana-discuss@openindiana.org > >> http://openindiana.org/mailman/listinfo/openindiana-discuss > > > > -- > > Predrag Zečević > > Technical Support Analyst > > 2e Systems GmbH > > > > Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 > > Mobile:+49 174 3109 288, Skype: predrag.zecevic > > E-mail:predrag.zece...@2e-systems.com > > > > Headquarter: 2e Systems GmbH, Königsteiner Str. 87, > > > > 65812 Bad Soden am Taunus, Germany > > > > Company registration: Amtsgericht Königstein (Germany), HRB 7303 > > Managing director:Phil Douglas > > > > http://www.2e-systems.com/ - Making your business fly! > > > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
no real options specified ... jadams@jadlaptop:~$ grep -v '^#' /etc/auto_master +auto_master /net-hosts-nosuid,nobrowse /homeauto_home-nobrowse jadams@jadlaptop:~$ more auto_master.ldif version: 1 DN: nisMapName=auto_master,dc=domain,dc=com objectClass: top objectClass: nisMap nisMapName: auto_master DN: cn=/net,nisMapName=auto_master,dc=domain,dc=com objectClass: nisObject cn: /net nismapentry: -hosts -nosuid,nobrowse nisMapName: auto_master DN: cn=/home,nisMapName=auto_master,dc=domain,dc=com objectClass: nisObject cn: /home nismapentry: auto_home -nobrowse nisMapName: auto_master (slightly sanitised, yes I know that "nisMap" is the deprecated version of the automount stuff) the issue is with the automount, not with mounting in general ... I can hard mount it as root and access as my user with no trouble, I just can't access it via automount. The Linux laptops are usually running nfs v3, but only because we beat them with sticks till they behave ... our Riverbeds cannot optimise nfs v4, and permissions/ownership can go haywire when talking between Linux and Solaris 10 as nfs v4. Jon On 18 February 2015 at 13:13, Predrag Zecevic [Unix Systems Administrator] < predrag.zece...@2e-systems.com> wrote: > Hi, > > not sure if it is relevant, but in Solaris user home dirs were on > /export/home while /home was reserved for automounter. > > Not knowing FreeNAS (but some Linux systems), /home is location of user > home dirs. > Maybe problem solution can be looked in that direction? > > Regards. > > > On 02/18/15 01:12 PM, Jonathan Adams wrote: > >> I have an OpenIndiana laptop, it's running a copy of OpenLDAP as a replica >> of an OpenLDAP on our work server (syncs whenever it connects) ... and it >> uses this OpenLDAP database to power it's automount. (not sure if this is >> of any relevance, but included for completeness) >> >> I've been using this system for years in this configuration, but recently >> some of our users had their home directories moved from a Solaris 10 >> server >> to a FreeNAS server. I noticed that I couldn't access their home >> directories using the automounted "/home" directory, it comes up >> "permission denied". I can however access the users home directory if I >> hard mount as root. >> >> Our Solaris 10 servers have no trouble accessing the automounted >> directories, our Linux laptops have no issue either ... >> >> Does anyone else have issues like this, or know of any checks that I can >> perform to see if I can find the fault? >> >> Ta >> >> Jon >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss >> >> > -- > Predrag Zečević > Technical Support Analyst > 2e Systems GmbH > > Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 > Mobile:+49 174 3109 288, Skype: predrag.zecevic > E-mail:predrag.zece...@2e-systems.com > > Headquarter: 2e Systems GmbH, Königsteiner Str. 87, > 65812 Bad Soden am Taunus, Germany > Company registration: Amtsgericht Königstein (Germany), HRB 7303 > Managing director:Phil Douglas > > http://www.2e-systems.com/ - Making your business fly! > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
Hi, not sure if it is relevant, but in Solaris user home dirs were on /export/home while /home was reserved for automounter. Not knowing FreeNAS (but some Linux systems), /home is location of user home dirs. Maybe problem solution can be looked in that direction? Regards. On 02/18/15 01:12 PM, Jonathan Adams wrote: I have an OpenIndiana laptop, it's running a copy of OpenLDAP as a replica of an OpenLDAP on our work server (syncs whenever it connects) ... and it uses this OpenLDAP database to power it's automount. (not sure if this is of any relevance, but included for completeness) I've been using this system for years in this configuration, but recently some of our users had their home directories moved from a Solaris 10 server to a FreeNAS server. I noticed that I couldn't access their home directories using the automounted "/home" directory, it comes up "permission denied". I can however access the users home directory if I hard mount as root. Our Solaris 10 servers have no trouble accessing the automounted directories, our Linux laptops have no issue either ... Does anyone else have issues like this, or know of any checks that I can perform to see if I can find the fault? Ta Jon ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss -- Predrag Zečević Technical Support Analyst 2e Systems GmbH Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 Mobile:+49 174 3109 288, Skype: predrag.zecevic E-mail:predrag.zece...@2e-systems.com Headquarter: 2e Systems GmbH, Königsteiner Str. 87, 65812 Bad Soden am Taunus, Germany Company registration: Amtsgericht Königstein (Germany), HRB 7303 Managing director:Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS Automount from FreeNAS Server
This sounds like the NFS Settings in the LDAP differ from those you used to mount the share manually. NFS version 4's LDAP Access and NFS version 3's rootsquash option can prevent root from having access to other Users Homes. FreeNas has some security Settings inplace to forbid root to access other Users homes. It May be that the solaris 10 servers and the Linux Laptops still use nfs3 and thus dont have those Security Measures inplace. Or dont have rootsquash in their default configs. If you need more help, I would need to know the Options NFS Client Uses to mount the shares. Greetings Till Jonathan Adams schrieb am Wednesday 18 February 2015 12.12:23: > I have an OpenIndiana laptop, it's running a copy of OpenLDAP as a replica > of an OpenLDAP on our work server (syncs whenever it connects) ... and it > uses this OpenLDAP database to power it's automount. (not sure if this is > of any relevance, but included for completeness) > > I've been using this system for years in this configuration, but recently > some of our users had their home directories moved from a Solaris 10 server > to a FreeNAS server. I noticed that I couldn't access their home > directories using the automounted "/home" directory, it comes up > "permission denied". I can however access the users home directory if I > hard mount as root. > > Our Solaris 10 servers have no trouble accessing the automounted > directories, our Linux laptops have no issue either ... > > Does anyone else have issues like this, or know of any checks that I can > perform to see if I can find the fault? > > Ta > > Jon > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] NFS Automount from FreeNAS Server
I have an OpenIndiana laptop, it's running a copy of OpenLDAP as a replica of an OpenLDAP on our work server (syncs whenever it connects) ... and it uses this OpenLDAP database to power it's automount. (not sure if this is of any relevance, but included for completeness) I've been using this system for years in this configuration, but recently some of our users had their home directories moved from a Solaris 10 server to a FreeNAS server. I noticed that I couldn't access their home directories using the automounted "/home" directory, it comes up "permission denied". I can however access the users home directory if I hard mount as root. Our Solaris 10 servers have no trouble accessing the automounted directories, our Linux laptops have no issue either ... Does anyone else have issues like this, or know of any checks that I can perform to see if I can find the fault? Ta Jon ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
