All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Bill Shannon <bill.shannon@sun.com>
Cc: autofs@linux.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: Ubuntu NFS automount problem
Date: Mon, 24 Nov 2008 11:00:57 -0500	[thread overview]
Message-ID: <492ACFB9.7060201@redhat.com> (raw)
In-Reply-To: <1227531120.2913.9.camel@zeus.themaw.net>

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

  parent reply	other threads:[~2008-11-24 16:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23  2:27 Ubuntu NFS automount problem Bill Shannon
2008-11-24  4:08 ` Ian Kent
2008-11-24  7:25   ` Bill Shannon
2008-11-24 12:52     ` Ian Kent
2008-11-24 15:42       ` Bill Shannon
2008-11-24 16:00       ` Peter Staubach [this message]
2008-11-24 16:26         ` Ian Kent
2008-11-24 20:31         ` Bill Shannon
2008-11-25  1:32           ` Ian Kent
2008-11-25 10:27             ` Ondrej Valousek
2008-11-25 11:27               ` Ian Kent
2008-11-25 11:44                 ` Ondrej Valousek
2008-11-25 12:11                   ` Ian Kent
2008-11-24 15:59     ` Bill Shannon
2008-11-24 17:43       ` Ian Kent
2008-11-24 20:35         ` Bill Shannon
2008-11-25  1:21           ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2008-11-25  1:10 Brent Callaghan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=492ACFB9.7060201@redhat.com \
    --to=staubach@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=bill.shannon@sun.com \
    --cc=raven@themaw.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.