All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: "Breitman, Jason" <Jason.Breitman@blackrock.com>
Cc: autofs@linux.kernel.org
Subject: Re: automount restart required
Date: Fri, 06 Nov 2009 09:49:33 +0800	[thread overview]
Message-ID: <4AF380AD.2060506@themaw.net> (raw)
In-Reply-To: <5FAC3462B446C244A45ED5303B61491111920A41@NYCPEXV005.na.blkint.com>

Breitman, Jason wrote:
> The map with the issues is prod-autofs.clients.common.
> I have included the contents below.
> There are about 20 stanzas, but I figured you get the point from the
> snippet I included.
> 
> One mistake I believe I made is that the map should be a direct map,
> (/-), and I made it a indirect map.
> I did not realize that there was such a difference until I looked at the
> source code for automount.
> I am no expert, but there is a mentionable difference between indirect
> and direct maps.
> Do you think that could be my issue?

Don't know, maybe.

Using an indirect mount with entries that have offsets instead of direct
maps is fine and is the only valid way to setup map entries that are
nested (ie. where there are mounts within another mount).

> 
> $ cat /etc/auto.master 
> #
> # : auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
> #
> # Sample auto.master file
> # This is an automounter map and it has the following format
> # key [ -mount-options-separated-by-comma ] location
> # For details of the format look at autofs(5).
> #/misc  /etc/auto.misc --timeout=60
> #/misc  /etc/auto.misc
> #/net   /etc/auto.net
> /u1             prod-autofs.u1                  -hard,intr
> /proj           prod-autofs.proj                -hard,intr
> /usr/local      prod-autofs-linux.local         -hard,intr
> /reports        prod-autofs.reports             -hard,intr
> /clients        prod-autofs.clients.common      -hard,intr

I presume below is your prod-autofs.clients.common?
It looks a bit broken but that may just be the way it's formatted.

> 
> Client1 /proj/space

So this is the end of the first entry?
Where is the mount location?

> Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \
>         /proj/pkg_test

Then where is the key for this entry and what is that path doing there
without a mount location?

Each indirect map entry (with offsets) should have a form:

key [/] location [/path location [/path location ....]]

or

key [[/] location] /path location [/path location [/path location ....]]

An un-escaped newline marks a new map entry.

If there are too many offsets in a single entry and they aren't nested
then you can turn the map entry into a direct map. If some do have
nesting then you can use a direct mount map entry up to the point of the
nesting and then use offsets in that entry for the mounts below it.

These entries don't appear to match this syntax but that could just be
the formatting imposed by the mail client.

> Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/pkg_test \
>         /proj/GPA/historical-data
> Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/GPA/historic
> al-data \
>         /d0/prod1/reports
> Client1-nfs.Client1.blackrock.com:/clients/Client10102/d0/prod1/reports
> \
>         /u1/d0/prod1/reports
> Client1-nfs.Client1.blackrock.com:/clients/Client10102/d0/prod1/reports
> \
>         /u1/prod/reports
> Client1-nfs.Client1.blackrock.com:/clients/Client10102/d0/prod1/reports
> \
>         /usr/local/bfm/std
> Client1-nfs.Client1.blackrock.com:/clients/Client10101/local/bfm/std \
>         /tmpint
> Client1-nfs.Client1.blackrock.com:/clients/Client10101/homes1/tmpint \
>         /apps
> Client1-nfs.Client1.blackrock.com:/clients/Client10101/local/bfm/apps \
>         /web/htdocs
> Client1-nfs.Client1.blackrock.com:/clients/Client10101/local/bfm/web/htd
> ocs
> Client2 /proj/space
> Client2-nfs.Client2.blackrock.com:/clients/Client20101/proj/space \
>         /proj/pkg_test
> Client2-nfs.Client2.blackrock.com:/clients/Client20101/proj/pkg_test \
>         /proj/GPA/historical-data
> Client2-nfs.Client2.blackrock.com:/clients/Client20101/proj/GPA/historic
> al-data \
>         /d0/prod1/reports
> Client2-nfs.Client2.blackrock.com:/clients/Client20102/d0/prod1/reports
> \
>         /u1/d0/prod1/reports
> Client2-nfs.Client2.blackrock.com:/clients/Client20102/d0/prod1/reports
> \
>         /u1/prod/reports
> Client2-nfs.Client2.blackrock.com:/clients/Client20102/d0/prod1/reports
> \
>         /usr/local/bfm/std
> Client2-nfs.Client2.blackrock.com:/clients/Client20101/local/bfm/std \
>         /tmpint
> Client2-nfs.Client2.blackrock.com:/clients/Client20101/homes1/tmpint \
>         /apps
> Client2-nfs.Client2.blackrock.com:/clients/Client20101/local/bfm/apps \
>         /web/htdocs
> Client2-nfs.Client2.blackrock.com:/clients/Client20101/local/bfm/web/htd
> ocs
> Client3 /proj/space
> Client3-nfs.Client3.blackrock.com:/clients/Client30103/proj/space \
>         /proj/pkg_test
> Client3-nfs.Client3.blackrock.com:/clients/Client30103/proj/pkg_test \
>         /proj/GPA/historical-data
> Client3-nfs.Client3.blackrock.com:/clients/Client30101/proj/GPA/historic
> al-data \
>         /d0/prod1/reports
> Client3-nfs.Client3.blackrock.com:/clients/Client30102/d0/prod1/reports
> \
>         /u1/d0/prod1/reports
> Client3-nfs.Client3.blackrock.com:/clients/Client30102/d0/prod1/reports
> \
>         /u1/prod/reports
> Client3-nfs.Client3.blackrock.com:/clients/Client30102/d0/prod1/reports
> \
>         /usr/local/bfm/std
> Client3-nfs.Client3.blackrock.com:/clients/Client30101/local/bfm/std \
>         /tmpint
> Client3-nfs.Client3.blackrock.com:/clients/Client30101/homes1/tmpint \
>         /apps
> Client3-nfs.Client3.blackrock.com:/clients/Client30101/local/bfm/apps \
>         /web/htdocs
> Client3-nfs.Client3.blackrock.com:/clients/Client30101/local/bfm/web/htd
> ocs
> Client4 /proj/space
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/rep/proj/space \
>      /proj/pkg_test
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/rep/proj/pkg_test
> \
>      /proj/GPA/historical-data
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/rep/proj/GPA/hist
> orical-data \
>      /d0/prod1/reports
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/rep/d0/prod1/repo
> rts \
>      /u1/d0/prod1/reports
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/rep/d0/prod1/repo
> rts \
>      /u1/prod/reports
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/rep/d0/prod1/repo
> rts \
>      /usr/local/bfm/std
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/other/local/bfm/s
> td \
>      /tmpint
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/norep/homes/tmpin
> t \
>      /web/htdocs
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/other/local/bfm/w
> eb/htdocs \
>      /apps
> Client4-nfs.Client4.blackrock.com:/clients/Client40101/other/local/bfm/a
> pps 
> 
> 
> Jason Breitman
> jason.breitman@blackrock.com
> 
> -----Original Message-----
> From: Ian Kent [mailto:raven@themaw.net] 
> Sent: Wednesday, November 04, 2009 8:59 PM
> To: Breitman, Jason
> Cc: autofs@linux.kernel.org
> Subject: Re: [autofs] automount restart required
> 
> Breitman, Jason wrote:
>> Issue:
>> Users and applications will not be able to get into one of the
>> directories in the direct map.
>> The system reports no such file or directory.
>> I can get to the mount point, but not any further.
> 
> Show me your maps.
> 
> Ian
> 
> THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.

  reply	other threads:[~2009-11-06  1:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 16:53 automount restart required Breitman, Jason
2009-11-04  1:55 ` Ian Kent
2009-11-04 21:43   ` Breitman, Jason
2009-11-05  1:48     ` Ian Kent
2009-11-05  1:58 ` Ian Kent
2009-11-06  0:55   ` Breitman, Jason
2009-11-06  1:49     ` Ian Kent [this message]
2009-11-10 15:56       ` Breitman, Jason
2009-11-16  3:13         ` Breitman, Jason
2009-11-16  8:40           ` Ian Kent

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=4AF380AD.2060506@themaw.net \
    --to=raven@themaw.net \
    --cc=Jason.Breitman@blackrock.com \
    --cc=autofs@linux.kernel.org \
    /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.