Ubuntu NFS automount problem

Ubuntu NFS automount problem

[Bill Shannon]

I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
I have an OpenSolaris 2008.11 server and a Solaris 10 server.
Both servers export NFS filesystems.

On my Ubuntu desktop, the autmounter doesn't want to automount hierarchical
filesystems.  I first noticed this with /home, but /net doesn't work either.

My OpenSolaris server is named "nissan".  My Solaris server is named "nissan2".

# showmount -e nissan
Export list for nissan:
/backup                 (everyone)
/backup/download        (everyone)
/export/home/admin      (everyone)
/backup/pictures        (everyone)
/export/home/shannon    (everyone)
/export/home            (everyone)
/export/home/readerware (everyone)
/backup2                (everyone)
/export/home/opt        (everyone)
# showmount -e nissan2
Export list for nissan2:
/export/home (everyone)
/backup      (everyone)
/backup2     (everyone)
# cat /etc/auto.net
*	-rw,intr	&:/
# ls /net/nissan
ls: cannot access /net/nissan: No such file or directory
# ls /net/nissan2
ls: cannot access /net/nissan2: No such file or directory
# ls /home/nissan
admin  opt  readerware	shannon
# ls /home/nissan/shannon
# ls /home/nissan2/shannon
(lots of files)

Of course I have all those hierarchical exports on OpenSolaris because
of separate zfs filesystems.

Has anyone else seen this with the Ubuntu automounter?  Is this a known bug?
I've spent over an hour searching the web and I can't find an explanation
for this problem.

Thanks for any help!

Re: Ubuntu NFS automount problem

[Ian Kent]

On Sat, 2008-11-22 at 18:27 -0800, Bill Shannon wrote:
> I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
> I have an OpenSolaris 2008.11 server and a Solaris 10 server.
> Both servers export NFS filesystems.
> 
> On my Ubuntu desktop, the autmounter doesn't want to automount hierarchical
> filesystems.  I first noticed this with /home, but /net doesn't work either.
> 
> My OpenSolaris server is named "nissan".  My Solaris server is named "nissan2".
> 
> # showmount -e nissan
> Export list for nissan:
> /backup                 (everyone)
> /backup/download        (everyone)
> /export/home/admin      (everyone)
> /backup/pictures        (everyone)
> /export/home/shannon    (everyone)
> /export/home            (everyone)
> /export/home/readerware (everyone)
> /backup2                (everyone)
> /export/home/opt        (everyone)
> # showmount -e nissan2
> Export list for nissan2:
> /export/home (everyone)
> /backup      (everyone)
> /backup2     (everyone)
> # cat /etc/auto.net
> *	-rw,intr	&:/

How is do you expect this to work, explain?

> # ls /net/nissan
> ls: cannot access /net/nissan: No such file or directory
> # ls /net/nissan2
> ls: cannot access /net/nissan2: No such file or directory
> # ls /home/nissan
> admin  opt  readerware	shannon
> # ls /home/nissan/shannon
> # ls /home/nissan2/shannon
> (lots of files)
> 
> Of course I have all those hierarchical exports on OpenSolaris because
> of separate zfs filesystems.
> 
> Has anyone else seen this with the Ubuntu automounter?  Is this a known bug?
> I've spent over an hour searching the web and I can't find an explanation
> for this problem.
> 
> Thanks for any help!
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs

Re: Ubuntu NFS automount problem

[Bill Shannon]

Ian Kent wrote:
> On Sat, 2008-11-22 at 18:27 -0800, Bill Shannon wrote:
>> I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
>> I have an OpenSolaris 2008.11 server and a Solaris 10 server.
>> Both servers export NFS filesystems.
>>
>> On my Ubuntu desktop, the autmounter doesn't want to automount hierarchical
>> filesystems.  I first noticed this with /home, but /net doesn't work either.
>>
>> My OpenSolaris server is named "nissan".  My Solaris server is named "nissan2".
>>
>> # showmount -e nissan
>> Export list for nissan:
>> /backup                 (everyone)
>> /backup/download        (everyone)
>> /export/home/admin      (everyone)
>> /backup/pictures        (everyone)
>> /export/home/shannon    (everyone)
>> /export/home            (everyone)
>> /export/home/readerware (everyone)
>> /backup2                (everyone)
>> /export/home/opt        (everyone)
>> # showmount -e nissan2
>> Export list for nissan2:
>> /export/home (everyone)
>> /backup      (everyone)
>> /backup2     (everyone)
>> # cat /etc/auto.net
>> *	-rw,intr	&:/
> 
> How is do you expect this to work, explain?

The simple answer is - the same way it works on Solaris and Mac OS.

I should see the following directories:

/net/nissan/backup
/net/nissan/backup/download
/net/nissan/backup/pictures
/net/nissan/export
/net/nissan/export/home
/net/nissan/export/home/shannon

and so on.

After autofs mounts nissan:/backup on /net/nissan, it then
needs to mount nissan:/backup/download on /net/nissan/backup/download.

And in the case of nissan:/export, there's nothing to mount on
/net/nissan/export, so autofs needs to create a pseudo-directory
that contains an entry for "home".

Understand?

Re: Ubuntu NFS automount problem

[Ian Kent]

On Sun, 2008-11-23 at 23:25 -0800, Bill Shannon wrote:
> Ian Kent wrote:
> > On Sat, 2008-11-22 at 18:27 -0800, Bill Shannon wrote:
> >> I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
> >> I have an OpenSolaris 2008.11 server and a Solaris 10 server.
> >> Both servers export NFS filesystems.
> >>
> >> On my Ubuntu desktop, the autmounter doesn't want to automount hierarchical
> >> filesystems.  I first noticed this with /home, but /net doesn't work either.
> >>
> >> My OpenSolaris server is named "nissan".  My Solaris server is named "nissan2".
> >>
> >> # showmount -e nissan
> >> Export list for nissan:
> >> /backup                 (everyone)
> >> /backup/download        (everyone)
> >> /export/home/admin      (everyone)
> >> /backup/pictures        (everyone)
> >> /export/home/shannon    (everyone)
> >> /export/home            (everyone)
> >> /export/home/readerware (everyone)
> >> /backup2                (everyone)
> >> /export/home/opt        (everyone)
> >> # showmount -e nissan2
> >> Export list for nissan2:
> >> /export/home (everyone)
> >> /backup      (everyone)
> >> /backup2     (everyone)
> >> # cat /etc/auto.net
> >> *	-rw,intr	&:/
> > 
> > How is do you expect this to work, explain?
> 
> The simple answer is - the same way it works on Solaris and Mac OS.

I asked you "how" is this supposed to work not "what" you think is is
supposed to be the result.

> 
> I should see the following directories:
> 
> /net/nissan/backup
> /net/nissan/backup/download
> /net/nissan/backup/pictures
> /net/nissan/export
> /net/nissan/export/home
> /net/nissan/export/home/shannon

I can't see how the above map entry can provide these mappings and if
you can't provide an accurate description of how the mounts are
constructed I can't tell you whether Linux autofs can, either do what
you expect or be updated to do what you expect.

> 
> and so on.
> 
> After autofs mounts nissan:/backup on /net/nissan, it then
> needs to mount nissan:/backup/download on /net/nissan/backup/download.
> 
> And in the case of nissan:/export, there's nothing to mount on
> /net/nissan/export, so autofs needs to create a pseudo-directory
> that contains an entry for "home".
> 
> Understand?

No, I don't understand at all, but that's because you've not provided
any useful information.

Where in the Solaris documentation is the behavior of this type of map
entry described.

Ian

Re: Ubuntu NFS automount problem

[Bill Shannon]

Ian Kent wrote:
> On Sun, 2008-11-23 at 23:25 -0800, Bill Shannon wrote:
>> Ian Kent wrote:
>>> On Sat, 2008-11-22 at 18:27 -0800, Bill Shannon wrote:
>>>> I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
>>>> I have an OpenSolaris 2008.11 server and a Solaris 10 server.
>>>> Both servers export NFS filesystems.
>>>>
>>>> On my Ubuntu desktop, the autmounter doesn't want to automount hierarchical
>>>> filesystems.  I first noticed this with /home, but /net doesn't work either.
>>>>
>>>> My OpenSolaris server is named "nissan".  My Solaris server is named "nissan2".
>>>>
>>>> # showmount -e nissan
>>>> Export list for nissan:
>>>> /backup                 (everyone)
>>>> /backup/download        (everyone)
>>>> /export/home/admin      (everyone)
>>>> /backup/pictures        (everyone)
>>>> /export/home/shannon    (everyone)
>>>> /export/home            (everyone)
>>>> /export/home/readerware (everyone)
>>>> /backup2                (everyone)
>>>> /export/home/opt        (everyone)
>>>> # showmount -e nissan2
>>>> Export list for nissan2:
>>>> /export/home (everyone)
>>>> /backup      (everyone)
>>>> /backup2     (everyone)
>>>> # cat /etc/auto.net
>>>> *	-rw,intr	&:/
>>> How is do you expect this to work, explain?
>> The simple answer is - the same way it works on Solaris and Mac OS.
> 
> I asked you "how" is this supposed to work not "what" you think is is
> supposed to be the result.

Sorry, I'm just *using* this software, not designing it.  The "how" is
up to you.

>> I should see the following directories:
>>
>> /net/nissan/backup
>> /net/nissan/backup/download
>> /net/nissan/backup/pictures
>> /net/nissan/export
>> /net/nissan/export/home
>> /net/nissan/export/home/shannon
> 
> I can't see how the above map entry can provide these mappings and if
> you can't provide an accurate description of how the mounts are
> constructed I can't tell you whether Linux autofs can, either do what
> you expect or be updated to do what you expect.

I'm sorry you don't understand.  I gave you the most complete description
of how this works that I can.  I'm not sure what's so confusing to you.

Under /net/<hostname> I want to see a filesystem hierarchy that matches
all the exported filesystems from the host.  If the host exports *every*
filesystem, then I would want to see a hierarchy that matches exactly
what I see on the host.  In most cases a host won't export everything,
so autofs has to fill in some parts of the hierarchy with pseudo-directories.

Do you see how the list of exported directories is not a flat namespace
but can actually be arranged into a hierarchy?  How some exported directories
appear "inside" other exported directories?

Maybe if you can explain more clearly what it is that's confusing you I
can help.

>> and so on.
>>
>> After autofs mounts nissan:/backup on /net/nissan, it then
>> needs to mount nissan:/backup/download on /net/nissan/backup/download.
>>
>> And in the case of nissan:/export, there's nothing to mount on
>> /net/nissan/export, so autofs needs to create a pseudo-directory
>> that contains an entry for "home".
>>
>> Understand?
> 
> No, I don't understand at all, but that's because you've not provided
> any useful information.
> 
> Where in the Solaris documentation is the behavior of this type of map
> entry described.

I don't know.  It's worked this way in Solaris for 20 years.  It's been
a long time since I've read the documentation.  Where did you look in
the Solaris documentation to figure this out?

Have you ever *tried* this on Solaris?  I think a little experimenting
would show you how it works.

I have to say, it's a bit disappointing that you don't understand how the
corresponding Solaris version works, since it's clearly the de facto
standard for this technology.

Re: Ubuntu NFS automount problem

[Peter Staubach]

Ian Kent wrote:
> On Sun, 2008-11-23 at 23:25 -0800, Bill Shannon wrote:
>   
>> Ian Kent wrote:
>>     
>>> On Sat, 2008-11-22 at 18:27 -0800, Bill Shannon wrote:
>>>       
>>>> I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
>>>> I have an OpenSolaris 2008.11 server and a Solaris 10 server.
>>>> Both servers export NFS filesystems.
>>>>
>>>> On my Ubuntu desktop, the autmounter doesn't want to automount hierarchical
>>>> filesystems.  I first noticed this with /home, but /net doesn't work either.
>>>>
>>>> My OpenSolaris server is named "nissan".  My Solaris server is named "nissan2".
>>>>
>>>> # showmount -e nissan
>>>> Export list for nissan:
>>>> /backup                 (everyone)
>>>> /backup/download        (everyone)
>>>> /export/home/admin      (everyone)
>>>> /backup/pictures        (everyone)
>>>> /export/home/shannon    (everyone)
>>>> /export/home            (everyone)
>>>> /export/home/readerware (everyone)
>>>> /backup2                (everyone)
>>>> /export/home/opt        (everyone)
>>>> # showmount -e nissan2
>>>> Export list for nissan2:
>>>> /export/home (everyone)
>>>> /backup      (everyone)
>>>> /backup2     (everyone)
>>>> # cat /etc/auto.net
>>>> *	-rw,intr	&:/
>>>>         
>>> How is do you expect this to work, explain?
>>>       
>> The simple answer is - the same way it works on Solaris and Mac OS.
>>     
>
> I asked you "how" is this supposed to work not "what" you think is is
> supposed to be the result.
>
>   
>> I should see the following directories:
>>
>> /net/nissan/backup
>> /net/nissan/backup/download
>> /net/nissan/backup/pictures
>> /net/nissan/export
>> /net/nissan/export/home
>> /net/nissan/export/home/shannon
>>     
>
> I can't see how the above map entry can provide these mappings and if
> you can't provide an accurate description of how the mounts are
> constructed I can't tell you whether Linux autofs can, either do what
> you expect or be updated to do what you expect.
>
>   
>> and so on.
>>
>> After autofs mounts nissan:/backup on /net/nissan, it then
>> needs to mount nissan:/backup/download on /net/nissan/backup/download.
>>
>> And in the case of nissan:/export, there's nothing to mount on
>> /net/nissan/export, so autofs needs to create a pseudo-directory
>> that contains an entry for "home".
>>
>> Understand?
>>     
>
> No, I don't understand at all, but that's because you've not provided
> any useful information.
>
> Where in the Solaris documentation is the behavior of this type of map
> entry described.

Bill, why aren't you using the -hosts map?  This would make the behavior
of Linux work like Solaris.  The map supplied will just mount "/" from
the server.  This may work for NFSv4, but will not work so well for NFSv2
and NFSv3.  You might also try forcing NFSv4 on the Ubuntu system.

       ps

Re: Ubuntu NFS automount problem

[Ian Kent]

On Mon, 2008-11-24 at 11:00 -0500, Peter Staubach wrote:
> Ian Kent wrote:
> > On Sun, 2008-11-23 at 23:25 -0800, Bill Shannon wrote:
> >   
> >> Ian Kent wrote:
> >>     
> >>> On Sat, 2008-11-22 at 18:27 -0800, Bill Shannon wrote:
> >>>       
> >>>> I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
> >>>> I have an OpenSolaris 2008.11 server and a Solaris 10 server.
> >>>> Both servers export NFS filesystems.
> >>>>
> >>>> On my Ubuntu desktop, the autmounter doesn't want to automount hierarchical
> >>>> filesystems.  I first noticed this with /home, but /net doesn't work either.
> >>>>
> >>>> My OpenSolaris server is named "nissan".  My Solaris server is named "nissan2".
> >>>>
> >>>> # showmount -e nissan
> >>>> Export list for nissan:
> >>>> /backup                 (everyone)
> >>>> /backup/download        (everyone)
> >>>> /export/home/admin      (everyone)
> >>>> /backup/pictures        (everyone)
> >>>> /export/home/shannon    (everyone)
> >>>> /export/home            (everyone)
> >>>> /export/home/readerware (everyone)
> >>>> /backup2                (everyone)
> >>>> /export/home/opt        (everyone)
> >>>> # showmount -e nissan2
> >>>> Export list for nissan2:
> >>>> /export/home (everyone)
> >>>> /backup      (everyone)
> >>>> /backup2     (everyone)
> >>>> # cat /etc/auto.net
> >>>> *	-rw,intr	&:/
> >>>>         
> >>> How is do you expect this to work, explain?
> >>>       
> >> The simple answer is - the same way it works on Solaris and Mac OS.
> >>     
> >
> > I asked you "how" is this supposed to work not "what" you think is is
> > supposed to be the result.
> >
> >   
> >> I should see the following directories:
> >>
> >> /net/nissan/backup
> >> /net/nissan/backup/download
> >> /net/nissan/backup/pictures
> >> /net/nissan/export
> >> /net/nissan/export/home
> >> /net/nissan/export/home/shannon
> >>     
> >
> > I can't see how the above map entry can provide these mappings and if
> > you can't provide an accurate description of how the mounts are
> > constructed I can't tell you whether Linux autofs can, either do what
> > you expect or be updated to do what you expect.
> >
> >   
> >> and so on.
> >>
> >> After autofs mounts nissan:/backup on /net/nissan, it then
> >> needs to mount nissan:/backup/download on /net/nissan/backup/download.
> >>
> >> And in the case of nissan:/export, there's nothing to mount on
> >> /net/nissan/export, so autofs needs to create a pseudo-directory
> >> that contains an entry for "home".
> >>
> >> Understand?
> >>     
> >
> > No, I don't understand at all, but that's because you've not provided
> > any useful information.
> >
> > Where in the Solaris documentation is the behavior of this type of map
> > entry described.
> 
> Bill, why aren't you using the -hosts map?  This would make the behavior
> of Linux work like Solaris.  The map supplied will just mount "/" from
> the server.  This may work for NFSv4, but will not work so well for NFSv2
> and NFSv3.  You might also try forcing NFSv4 on the Ubuntu system.

Which raises the other question I have about the export map from the
server above.

I thought that NFSv4 export tree was based on a single root, "/", and
everthing else was subordinate to that. So how would one go about
merging the file systems exported above as NFSv4 export tree?

Anyone?

The other problem, of course, is that Bill would need the ubuntu autofs5
package to use NFSv4 in this way and it probably still has the 5.0.3 bug
you reported (and we fixed) so ubuntu would need to add the patch to fix
that. And the mount tree would be a little different to what is
described above too.

Ian

Re: Ubuntu NFS automount problem

[Bill Shannon]

Peter Staubach wrote:
> Bill, why aren't you using the -hosts map?

That's a good question...

I don't remember how I got to this point, but ...

I just tried using -hosts, but it doesn't seem to be working:

vostro# cat /etc/auto.master
# $Id: auto.master,v 1.2 1997/10/06 21:52:03 hpa Exp $
# Sample auto.master file
# Format of this file:
# mountpoint map options
# For details of the format look at autofs(8).
# /misc	/etc/auto.misc	--timeout=60
/home	/etc/auto.home	-nosuid
#/net	/etc/auto.net	-nosuid
/net	-hosts		-nosuid
#/-	/etc/auto.direct	-nosuid
vostro# /etc/init.d/autofs reload
Reloading automounter: checking for changes ...
Reloading automounter map for: /home
Stopping automounter for: /smb
vostro# ls /net/nissan
ls: cannot access /net/nissan: No such file or directory
vostro# /etc/init.d/autofs restart
Stopping automounter:
   Couldn't stop automount for /home done.
Starting automounter:
  failed to start automount point /home
  done.
vostro# /etc/init.d/autofs reload
Reloading automounter: checking for changes ...
Reloading automounter map for: /home
vostro# ls /net/nissan
ls: cannot access /net/nissan: No such file or directory
vostro# grep nissan /etc/hosts
192.168.1.2	nissan

I think that's the reason I ended up with an auto.net map,
although it now seems likely that it never worked as intended.

I started chasing this problem because my auto.home map wasn't
working, which I now understand is the expected behavior based
on the way I'm now exporting my /export/home filesystems.  My
mistake.

I just fixed my auto.home map using multimounts.

Still, any hints as to why the -hosts pseudo-map isn't working
would be appreciated.  Are you sure it's *supposed* to work?
It's not documented in the man page.

I think this is the version of autofs I have:

vostro# dpkg-query -l 'autofs*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  autofs         4.1.4+debian-2 kernel-based automounter for Linux

Is there an "autofs5" package I should install instead?

Thanks for your help!

Re: Ubuntu NFS automount problem

[Ian Kent]

On Mon, 2008-11-24 at 12:31 -0800, Bill Shannon wrote:
> Peter Staubach wrote:
> > Bill, why aren't you using the -hosts map?
> 
> That's a good question...
> 
> I don't remember how I got to this point, but ...
> 
> I just tried using -hosts, but it doesn't seem to be working:
> 
> vostro# cat /etc/auto.master
> # $Id: auto.master,v 1.2 1997/10/06 21:52:03 hpa Exp $
> # Sample auto.master file
> # Format of this file:
> # mountpoint map options
> # For details of the format look at autofs(8).
> # /misc	/etc/auto.misc	--timeout=60
> /home	/etc/auto.home	-nosuid
> #/net	/etc/auto.net	-nosuid
> /net	-hosts		-nosuid
> #/-	/etc/auto.direct	-nosuid
> vostro# /etc/init.d/autofs reload
> Reloading automounter: checking for changes ...
> Reloading automounter map for: /home
> Stopping automounter for: /smb
> vostro# ls /net/nissan
> ls: cannot access /net/nissan: No such file or directory
> vostro# /etc/init.d/autofs restart
> Stopping automounter:
>    Couldn't stop automount for /home done.
> Starting automounter:
>   failed to start automount point /home
>   done.
> vostro# /etc/init.d/autofs reload
> Reloading automounter: checking for changes ...
> Reloading automounter map for: /home
> vostro# ls /net/nissan
> ls: cannot access /net/nissan: No such file or directory
> vostro# grep nissan /etc/hosts
> 192.168.1.2	nissan
> 
> I think that's the reason I ended up with an auto.net map,
> although it now seems likely that it never worked as intended.
> 
> I started chasing this problem because my auto.home map wasn't
> working, which I now understand is the expected behavior based
> on the way I'm now exporting my /export/home filesystems.  My
> mistake.
> 
> I just fixed my auto.home map using multimounts.
> 
> Still, any hints as to why the -hosts pseudo-map isn't working
> would be appreciated.  Are you sure it's *supposed* to work?
> It's not documented in the man page.
> 
> I think this is the version of autofs I have:
> 
> vostro# dpkg-query -l 'autofs*'
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> ||/ Name           Version        Description
> +++-==============-==============-============================================
> ii  autofs         4.1.4+debian-2 kernel-based automounter for Linux

Yep, that's version 4.

> 
> Is there an "autofs5" package I should install instead?

I'm not sure.

There is an autofs5 in the package pool on the mirrors but I can't tell
which release it belongs to.

Perhaps an "apt-cache search" will give the answer.

Ian

Re: Ubuntu NFS automount problem

[Ondrej Valousek]

Ian,
So what is the conclusion in terms of NFSv4 compatibility? Will the 
-hosts map work in autofs5?
Thanks,
Ondrej

Ian Kent wrote:
> On Mon, 2008-11-24 at 12:31 -0800, Bill Shannon wrote:
>   
>> Peter Staubach wrote:
>>     
>>> Bill, why aren't you using the -hosts map?
>>>       
>> That's a good question...
>>
>> I don't remember how I got to this point, but ...
>>
>> I just tried using -hosts, but it doesn't seem to be working:
>>
>> vostro# cat /etc/auto.master
>> # $Id: auto.master,v 1.2 1997/10/06 21:52:03 hpa Exp $
>> # Sample auto.master file
>> # Format of this file:
>> # mountpoint map options
>> # For details of the format look at autofs(8).
>> # /misc	/etc/auto.misc	--timeout=60
>> /home	/etc/auto.home	-nosuid
>> #/net	/etc/auto.net	-nosuid
>> /net	-hosts		-nosuid
>> #/-	/etc/auto.direct	-nosuid
>> vostro# /etc/init.d/autofs reload
>> Reloading automounter: checking for changes ...
>> Reloading automounter map for: /home
>> Stopping automounter for: /smb
>> vostro# ls /net/nissan
>> ls: cannot access /net/nissan: No such file or directory
>> vostro# /etc/init.d/autofs restart
>> Stopping automounter:
>>    Couldn't stop automount for /home done.
>> Starting automounter:
>>   failed to start automount point /home
>>   done.
>> vostro# /etc/init.d/autofs reload
>> Reloading automounter: checking for changes ...
>> Reloading automounter map for: /home
>> vostro# ls /net/nissan
>> ls: cannot access /net/nissan: No such file or directory
>> vostro# grep nissan /etc/hosts
>> 192.168.1.2	nissan
>>
>> I think that's the reason I ended up with an auto.net map,
>> although it now seems likely that it never worked as intended.
>>
>> I started chasing this problem because my auto.home map wasn't
>> working, which I now understand is the expected behavior based
>> on the way I'm now exporting my /export/home filesystems.  My
>> mistake.
>>
>> I just fixed my auto.home map using multimounts.
>>
>> Still, any hints as to why the -hosts pseudo-map isn't working
>> would be appreciated.  Are you sure it's *supposed* to work?
>> It's not documented in the man page.
>>
>> I think this is the version of autofs I have:
>>
>> vostro# dpkg-query -l 'autofs*'
>> Desired=Unknown/Install/Remove/Purge/Hold
>> | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
>> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
>> ||/ Name           Version        Description
>> +++-==============-==============-============================================
>> ii  autofs         4.1.4+debian-2 kernel-based automounter for Linux
>>     
>
> Yep, that's version 4.
>
>   
>> Is there an "autofs5" package I should install instead?
>>     
>
> I'm not sure.
>
> There is an autofs5 in the package pool on the mirrors but I can't tell
> which release it belongs to.
>
> Perhaps an "apt-cache search" will give the answer.
>
> Ian
>
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
>   

Re: Ubuntu NFS automount problem

[Ian Kent]

On Tue, 2008-11-25 at 11:27 +0100, Ondrej Valousek wrote:
> Ian,
> So what is the conclusion in terms of NFSv4 compatibility? Will the 
> -hosts map work in autofs5?

I don't think so, not the hosts map, since the export path doesn't match
the mount location path. There are other difficulties as well such as
having to modify paths in the export list as we go. However, exports
with "nohide" option should be automounted by the kernel client and not
confuse autofs so that part is ok with 5.0.4 or if the patch which deals
with this has been applied to 5.0.3.

This is something I need to work on.

> Thanks,
> Ondrej
> 
> Ian Kent wrote:
> > On Mon, 2008-11-24 at 12:31 -0800, Bill Shannon wrote:
> >   
> >> Peter Staubach wrote:
> >>     
> >>> Bill, why aren't you using the -hosts map?
> >>>       
> >> That's a good question...
> >>
> >> I don't remember how I got to this point, but ...
> >>
> >> I just tried using -hosts, but it doesn't seem to be working:
> >>
> >> vostro# cat /etc/auto.master
> >> # $Id: auto.master,v 1.2 1997/10/06 21:52:03 hpa Exp $
> >> # Sample auto.master file
> >> # Format of this file:
> >> # mountpoint map options
> >> # For details of the format look at autofs(8).
> >> # /misc	/etc/auto.misc	--timeout=60
> >> /home	/etc/auto.home	-nosuid
> >> #/net	/etc/auto.net	-nosuid
> >> /net	-hosts		-nosuid
> >> #/-	/etc/auto.direct	-nosuid
> >> vostro# /etc/init.d/autofs reload
> >> Reloading automounter: checking for changes ...
> >> Reloading automounter map for: /home
> >> Stopping automounter for: /smb
> >> vostro# ls /net/nissan
> >> ls: cannot access /net/nissan: No such file or directory
> >> vostro# /etc/init.d/autofs restart
> >> Stopping automounter:
> >>    Couldn't stop automount for /home done.
> >> Starting automounter:
> >>   failed to start automount point /home
> >>   done.
> >> vostro# /etc/init.d/autofs reload
> >> Reloading automounter: checking for changes ...
> >> Reloading automounter map for: /home
> >> vostro# ls /net/nissan
> >> ls: cannot access /net/nissan: No such file or directory
> >> vostro# grep nissan /etc/hosts
> >> 192.168.1.2	nissan
> >>
> >> I think that's the reason I ended up with an auto.net map,
> >> although it now seems likely that it never worked as intended.
> >>
> >> I started chasing this problem because my auto.home map wasn't
> >> working, which I now understand is the expected behavior based
> >> on the way I'm now exporting my /export/home filesystems.  My
> >> mistake.
> >>
> >> I just fixed my auto.home map using multimounts.
> >>
> >> Still, any hints as to why the -hosts pseudo-map isn't working
> >> would be appreciated.  Are you sure it's *supposed* to work?
> >> It's not documented in the man page.
> >>
> >> I think this is the version of autofs I have:
> >>
> >> vostro# dpkg-query -l 'autofs*'
> >> Desired=Unknown/Install/Remove/Purge/Hold
> >> | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
> >> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> >> ||/ Name           Version        Description
> >> +++-==============-==============-============================================
> >> ii  autofs         4.1.4+debian-2 kernel-based automounter for Linux
> >>     
> >
> > Yep, that's version 4.
> >
> >   
> >> Is there an "autofs5" package I should install instead?
> >>     
> >
> > I'm not sure.
> >
> > There is an autofs5 in the package pool on the mirrors but I can't tell
> > which release it belongs to.
> >
> > Perhaps an "apt-cache search" will give the answer.
> >
> > Ian
> >
> >
> > _______________________________________________
> > autofs mailing list
> > autofs@linux.kernel.org
> > http://linux.kernel.org/mailman/listinfo/autofs
> >   
> 

Re: Ubuntu NFS automount problem

[Ondrej Valousek]

> I don't think so, not the hosts map, since the export path doesn't match
> the mount location path. There are other difficulties as well such as
> having to modify paths in the export list as we go. However, exports
> with "nohide" option should be automounted by the kernel client and not
> confuse autofs so that part is ok with 5.0.4 or if the patch which deals
> with this has been applied to 5.0.3.
>
> This is something I need to work on.
>
>   
So since the "nohide" option is a must for the Linux-based NFSv4 server,
it will work (for most of the people)...
Thanks,
Ondrej

Re: Ubuntu NFS automount problem

[Ian Kent]

On Tue, 2008-11-25 at 12:44 +0100, Ondrej Valousek wrote:
> > I don't think so, not the hosts map, since the export path doesn't match
> > the mount location path. There are other difficulties as well such as
> > having to modify paths in the export list as we go. However, exports
> > with "nohide" option should be automounted by the kernel client and not
> > confuse autofs so that part is ok with 5.0.4 or if the patch which deals
> > with this has been applied to 5.0.3.
> >
> > This is something I need to work on.
> >
> >   
> So since the "nohide" option is a must for the Linux-based NFSv4 server,
> it will work (for most of the people)...

Don't forget that I need to remove the initial part of each export path
that corresponds to the NFSv4 export root which hasn't been done yet.

> Thanks,
> Ondrej

Re: Ubuntu NFS automount problem

[Bill Shannon]

Bill Shannon wrote:
>>> # cat /etc/auto.net
>>> *    -rw,intr    &:/
>>
>> How is do you expect this to work, explain?

Ok, maybe the question you meant to ask is "how is the above entry
supposed to achieve the effect you desire".

That's a good question.

Going back to Solaris, I see that /net is handled by a special
auto.master entry:

/net	-hosts	-nosuid

I'd forgotten all about that.

I just tried that on Linux with autofs and it doesn't seem to work.
Is there a Linux equivalent for the "-hosts" pseudo-map on Solaris?

I'm having the same problem with the corresponding entry in my
my auto.home map.  I guess exporting each individual home directory
from zfs isn't going to work the same way exporting the entire /export/home
directory works.  I guess I'll have to find a better way to handle that...

Re: Ubuntu NFS automount problem

[Ian Kent]

On Mon, 2008-11-24 at 07:59 -0800, Bill Shannon wrote:
> Bill Shannon wrote:
> >>> # cat /etc/auto.net
> >>> *    -rw,intr    &:/
> >>
> >> How is do you expect this to work, explain?
> 
> Ok, maybe the question you meant to ask is "how is the above entry
> supposed to achieve the effect you desire".
> 
> That's a good question.

And the answer is "it doesn't".
At least not on Solaris 9 or Linux.
I don't know about OpenSolaris or Solaris 10.

The reason I was confused is because of the internal contradictions in
you original two postings.

But, if you could have described the semantic rules which allowed that
apparent contradiction work the way you described then I would have been
happy to listen.

> 
> Going back to Solaris, I see that /net is handled by a special
> auto.master entry:
> 
> /net	-hosts	-nosuid
> 
> I'd forgotten all about that.
> 
> I just tried that on Linux with autofs and it doesn't seem to work.
> Is there a Linux equivalent for the "-hosts" pseudo-map on Solaris?

Yes, with autofs version 4 use "/net /etc/auto.net" in the master map
which generally should work the way you expect. The internal hosts map
is available in autofs version 5, which I suspect may be called autofs5
in ubuntu.

> 
> I'm having the same problem with the corresponding entry in my
> my auto.home map.  I guess exporting each individual home directory
> from zfs isn't going to work the same way exporting the entire /export/home
> directory works.  I guess I'll have to find a better way to handle that...

I don't know how zfs may change any of this either.

A wildcard map for an indirect map, which home directories usually are,
might be:

*	<home directory server>:/<home directory base directory>/&

Re: Ubuntu NFS automount problem

[Bill Shannon]

Ian Kent wrote:
>> I just tried that on Linux with autofs and it doesn't seem to work.
>> Is there a Linux equivalent for the "-hosts" pseudo-map on Solaris?
> 
> Yes, with autofs version 4 use "/net /etc/auto.net" in the master map
> which generally should work the way you expect. The internal hosts map
> is available in autofs version 5, which I suspect may be called autofs5
> in ubuntu.

Ah ha!

For reasons I no longer remember, I replaced the standard Ubuntu
/etc/auto.net with my (stupidly wrong) version some time ago.
I just rediscovered the original Ubuntu version and it seems to be
working fine.

Thanks for your help, and sorry for the stupid questions...

Re: Ubuntu NFS automount problem

[Ian Kent]

On Mon, 2008-11-24 at 12:35 -0800, Bill Shannon wrote:
> Ian Kent wrote:
> >> I just tried that on Linux with autofs and it doesn't seem to work.
> >> Is there a Linux equivalent for the "-hosts" pseudo-map on Solaris?
> > 
> > Yes, with autofs version 4 use "/net /etc/auto.net" in the master map
> > which generally should work the way you expect. The internal hosts map
> > is available in autofs version 5, which I suspect may be called autofs5
> > in ubuntu.
> 
> Ah ha!
> 
> For reasons I no longer remember, I replaced the standard Ubuntu
> /etc/auto.net with my (stupidly wrong) version some time ago.
> I just rediscovered the original Ubuntu version and it seems to be
> working fine.

Great.

> 
> Thanks for your help, and sorry for the stupid questions...

That's fine. Questions are no problem, it's the statements of alleged
"fact" that tend to push my buttons, I can't help being harsh on those
occasions.

Apologies also.

Ian

Re: Ubuntu NFS automount problem

[Brent Callaghan]

Normally we'd expect to see something like this in an auto.master map:

	/net			-hosts		-nobrowse,nosuid
	/home			auto_home	-nobrowse

The -hosts built-in map uses the mount protocol to derive a list of
exports (as Bill did with showmount) and it'll mount the whole
hierarchy if you touch all the triggers, i.e. it'll mount "/backup"
then "/backup/download".  For some reason, it appears that
the /net map on the client isn't working at all.  Bill, is there
an autofs mount on /net ?

I wouldn't normally expect hierarchical home directory mounts
unless the map entry in auto_home is specifically configured
to provide it, e.g.

	shannon  \
		/		nissan:/export/home/shannon \
		/stuff	nissan:/export/home/shannon/stuff

However, normally you should expect /home to be set up
with the username rather than the hostname as the key, e.g.
you should be trying to access "/home/shannon" or somesuch
rather than "/home/nissan".

	Brent

	


>
> On Sat, 2008-11-22 at 18:27 -0800, Bill Shannon wrote:
>> I'm running Ubuntu 8.04 (Hardy Heron) on my desktop at home.
>> I have an OpenSolaris 2008.11 server and a Solaris 10 server.
>> Both servers export NFS filesystems.
>>
>> On my Ubuntu desktop, the autmounter doesn't want to automount  
>> hierarchical
>> filesystems.  I first noticed this with /home, but /net doesn't  
>> work either.
>>
>> My OpenSolaris server is named "nissan".  My Solaris server is  
>> named "nissan2".
>>
>> # showmount -e nissan
>> Export list for nissan:
>> /backup                 (everyone)
>> /backup/download        (everyone)
>> /export/home/admin      (everyone)
>> /backup/pictures        (everyone)
>> /export/home/shannon    (everyone)
>> /export/home            (everyone)
>> /export/home/readerware (everyone)
>> /backup2                (everyone)
>> /export/home/opt        (everyone)
>> # showmount -e nissan2
>> Export list for nissan2:
>> /export/home (everyone)
>> /backup      (everyone)
>> /backup2     (everyone)
>> # cat /etc/auto.net
>> *	-rw,intr	&:/
>
> How is do you expect this to work, explain?
>
>> # ls /net/nissan
>> ls: cannot access /net/nissan: No such file or directory
>> # ls /net/nissan2
>> ls: cannot access /net/nissan2: No such file or directory
>> # ls /home/nissan
>> admin  opt  readerware	shannon
>> # ls /home/nissan/shannon
>> # ls /home/nissan2/shannon
>> (lots of files)
>>
>> Of course I have all those hierarchical exports on OpenSolaris  
>> because
>> of separate zfs filesystems.
>>
>> Has anyone else seen this with the Ubuntu automounter?  Is this a  
>> known bug?
>> I've spent over an hour searching the web and I can't find an  
>> explanation
>> for this problem.
>>
>> Thanks for any help!
>>
>> _______________________________________________