* automount restart required @ 2009-11-03 16:53 Breitman, Jason 2009-11-04 1:55 ` Ian Kent 2009-11-05 1:58 ` Ian Kent 0 siblings, 2 replies; 10+ messages in thread From: Breitman, Jason @ 2009-11-03 16:53 UTC (permalink / raw) To: autofs Operating System: RHEL 5.3 (32 bit) kernel package: kernel-2.6.18-128.el5 autofs package: autofs-5.0.1-0.rc2.131.el5_4.1 nfs-utils package: nfs-utils-1.0.9-40.el5 Map Type: Direct Map stored in NIS 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. * I can not reproduce the issue on demand. ** The issue does happen on multiple hosts with the same build. Resolution: /etc/init.d/autofs restart Question: I noticed much later versions of autofs on Fedora. (autofs-5.0.4-XXX) I also read the changelog and there are many fixes that might be considered a solution to my problem. Bottom line is what is the most stable package of autofs that I should be using on my RHEL 5.3 Systems. I understand that RHEL support may be affected, but would be willing to deal with those issues. Thanks. Jason Breitman jason.breitman@blackrock.com 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 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:58 ` Ian Kent 1 sibling, 1 reply; 10+ messages in thread From: Ian Kent @ 2009-11-04 1:55 UTC (permalink / raw) To: Breitman, Jason; +Cc: autofs Breitman, Jason wrote: > Operating System: RHEL 5.3 (32 bit) > > kernel package: kernel-2.6.18-128.el5 > > autofs package: autofs-5.0.1-0.rc2.131.el5_4.1 > > nfs-utils package: nfs-utils-1.0.9-40.el5 > > Map Type: Direct Map stored in NIS > > 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. > > * I can not reproduce the issue on demand. > ** The issue does happen on multiple hosts with the same build. > > Resolution: > /etc/init.d/autofs restart > > Question: > I noticed much later versions of autofs on Fedora. (autofs-5.0.4-XXX) > I also read the changelog and there are many fixes that might be > considered a solution to my problem. I doubt it. The RHEL version you have is actually quite close to the Fedora version. > Bottom line is what is the most stable package of autofs that I should > be using on my RHEL 5.3 Systems. The version you have is the latest RHEL version. I'm not aware of the problem you describe so log a bug and include your maps, a debug log showing the problem and any other information like how often it happens. > I understand that RHEL support may be affected, but would be willing to > deal with those issues. So now there is more than one issue, what are the other issues? > > Thanks. > > Jason Breitman > jason.breitman@blackrock.com > > 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. > > _______________________________________________ > autofs mailing list > autofs@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/autofs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-04 1:55 ` Ian Kent @ 2009-11-04 21:43 ` Breitman, Jason 2009-11-05 1:48 ` Ian Kent 0 siblings, 1 reply; 10+ messages in thread From: Breitman, Jason @ 2009-11-04 21:43 UTC (permalink / raw) To: autofs Am I reading the version number wrong or is there a different numbering scheme inside of RHEL then in Fedora? http://mirrors.kernel.org/fedora/releases/11/Everything/i386/os/Packages /autofs-5.0.4-24.i586.rpm I will work on submitting a bug. All I meant by issues is that I would rather deal with losing my official Redhat Support by using a Redhat unapproved, yet more stable, version of autofs then continue to use the Redhat approved autofs package and have automount issues. Hopefully that makes sense. Jason Breitman jason.breitman@blackrock.com -----Original Message----- From: Ian Kent [mailto:raven@themaw.net] Sent: Tuesday, November 03, 2009 8:56 PM To: Breitman, Jason Cc: autofs@linux.kernel.org Subject: Re: [autofs] automount restart required Breitman, Jason wrote: > Operating System: RHEL 5.3 (32 bit) > > kernel package: kernel-2.6.18-128.el5 > > autofs package: autofs-5.0.1-0.rc2.131.el5_4.1 > > nfs-utils package: nfs-utils-1.0.9-40.el5 > > Map Type: Direct Map stored in NIS > > 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. > > * I can not reproduce the issue on demand. > ** The issue does happen on multiple hosts with the same build. > > Resolution: > /etc/init.d/autofs restart > > Question: > I noticed much later versions of autofs on Fedora. (autofs-5.0.4-XXX) > I also read the changelog and there are many fixes that might be > considered a solution to my problem. I doubt it. The RHEL version you have is actually quite close to the Fedora version. > Bottom line is what is the most stable package of autofs that I should > be using on my RHEL 5.3 Systems. The version you have is the latest RHEL version. I'm not aware of the problem you describe so log a bug and include your maps, a debug log showing the problem and any other information like how often it happens. > I understand that RHEL support may be affected, but would be willing to > deal with those issues. So now there is more than one issue, what are the other issues? > > Thanks. > > Jason Breitman > jason.breitman@blackrock.com > > 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. > > _______________________________________________ > autofs mailing list > autofs@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/autofs 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-04 21:43 ` Breitman, Jason @ 2009-11-05 1:48 ` Ian Kent 0 siblings, 0 replies; 10+ messages in thread From: Ian Kent @ 2009-11-05 1:48 UTC (permalink / raw) To: Breitman, Jason; +Cc: autofs Breitman, Jason wrote: > Am I reading the version number wrong or is there a different numbering > scheme inside of RHEL then in Fedora? Don't be difficult. All the important fixes are included in the RHEL-5 revision. In fact, a lot of the time the fixes in the upstream package come from work on RHEL reported bugs. Admittedly, it can be a while before they make it into a RHEL release due to the process but the RHEL-5 version you are using is very close to the Fedora version. > > http://mirrors.kernel.org/fedora/releases/11/Everything/i386/os/Packages > /autofs-5.0.4-24.i586.rpm > > I will work on submitting a bug. > > All I meant by issues is that I would rather deal with losing my > official Redhat Support by using a Redhat unapproved, yet more stable, > version of autofs then continue to use the Redhat approved autofs > package and have automount issues. Hopefully that makes sense. > > > Jason Breitman > jason.breitman@blackrock.com > > -----Original Message----- > From: Ian Kent [mailto:raven@themaw.net] > Sent: Tuesday, November 03, 2009 8:56 PM > To: Breitman, Jason > Cc: autofs@linux.kernel.org > Subject: Re: [autofs] automount restart required > > Breitman, Jason wrote: >> Operating System: RHEL 5.3 (32 bit) >> >> kernel package: kernel-2.6.18-128.el5 >> >> autofs package: autofs-5.0.1-0.rc2.131.el5_4.1 >> >> nfs-utils package: nfs-utils-1.0.9-40.el5 >> >> Map Type: Direct Map stored in NIS >> >> 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. >> >> * I can not reproduce the issue on demand. >> ** The issue does happen on multiple hosts with the same build. >> >> Resolution: >> /etc/init.d/autofs restart >> >> Question: >> I noticed much later versions of autofs on Fedora. (autofs-5.0.4-XXX) >> I also read the changelog and there are many fixes that might be >> considered a solution to my problem. > > I doubt it. > The RHEL version you have is actually quite close to the Fedora version. > >> Bottom line is what is the most stable package of autofs that I should >> be using on my RHEL 5.3 Systems. > > The version you have is the latest RHEL version. > I'm not aware of the problem you describe so log a bug and include your > maps, a debug log showing the problem and any other information like how > often it happens. > >> I understand that RHEL support may be affected, but would be willing > to >> deal with those issues. > > So now there is more than one issue, what are the other issues? > >> Thanks. >> >> Jason Breitman >> jason.breitman@blackrock.com >> >> 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. >> _______________________________________________ >> autofs mailing list >> autofs@linux.kernel.org >> http://linux.kernel.org/mailman/listinfo/autofs > > > 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. > > _______________________________________________ > autofs mailing list > autofs@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/autofs ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-03 16:53 automount restart required Breitman, Jason 2009-11-04 1:55 ` Ian Kent @ 2009-11-05 1:58 ` Ian Kent 2009-11-06 0:55 ` Breitman, Jason 1 sibling, 1 reply; 10+ messages in thread From: Ian Kent @ 2009-11-05 1:58 UTC (permalink / raw) To: Breitman, Jason; +Cc: autofs 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-05 1:58 ` Ian Kent @ 2009-11-06 0:55 ` Breitman, Jason 2009-11-06 1:49 ` Ian Kent 0 siblings, 1 reply; 10+ messages in thread From: Breitman, Jason @ 2009-11-06 0:55 UTC (permalink / raw) To: Ian Kent; +Cc: autofs 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? $ 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 Client1 /proj/space Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \ /proj/pkg_test 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-06 0:55 ` Breitman, Jason @ 2009-11-06 1:49 ` Ian Kent 2009-11-10 15:56 ` Breitman, Jason 0 siblings, 1 reply; 10+ messages in thread From: Ian Kent @ 2009-11-06 1:49 UTC (permalink / raw) To: Breitman, Jason; +Cc: autofs 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-06 1:49 ` Ian Kent @ 2009-11-10 15:56 ` Breitman, Jason 2009-11-16 3:13 ` Breitman, Jason 0 siblings, 1 reply; 10+ messages in thread From: Breitman, Jason @ 2009-11-10 15:56 UTC (permalink / raw) To: Ian Kent; +Cc: autofs I will give an example of 1 stanza to help provide clarity of the map. /clients/CLIENT1 is the offset Once logged into a host you can cd to /clients/CLIENT1/proj/space /clients/CLIENT1/proj/pkg_test /clients/CLIENT1/proj/GPA/historical-data /clients/CLIENT1/d0/prod1/reports /clients/CLIENT1/u1/prod/reports /clients/CLIENT1/usr/local/bfm/std /clients/CLIENT1/tmpint /clients/CLIENT1/apps /clients/CLIENT1/web/htdocs All mounts are under the offset /clients/CLIENT1. I hope I am clear in my explanation. /etc/auto.master has the below entry /clients prod-autofs.clients.common -hard,intr prod-autofs.clients.common has the below entry Client1 /proj/space Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \ /proj/pkg_test 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 I thought my mistake might have been that /etc/auto.master should look like (indirect vs. direct map) /- prod-autofs.clients.common -hard,intr and prod-autofs.clients.common should look like /clients/Client1 \ /proj/space Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \ /proj/pkg_test 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 Please say if the formatting gets garbled and I will figure out some other way to get you the map entries. Jason Breitman jason.breitman@blackrock.com -----Original Message----- From: Ian Kent [mailto:raven@themaw.net] Sent: Thursday, November 05, 2009 8:50 PM To: Breitman, Jason Cc: autofs@linux.kernel.org Subject: Re: [autofs] automount restart required 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. 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-10 15:56 ` Breitman, Jason @ 2009-11-16 3:13 ` Breitman, Jason 2009-11-16 8:40 ` Ian Kent 0 siblings, 1 reply; 10+ messages in thread From: Breitman, Jason @ 2009-11-16 3:13 UTC (permalink / raw) To: autofs It appears that there are a few negatives to using direct maps so I have been evaluating other options. You must restart autofs anytime updates are made to the direct map. All entries in the direct map show up in /proc/mounts and I believe coincide with a mount which will cause a strain on the NFS Server. (mount storm) I noticed a difference between /etc/mtab and /proc/mounts and hope someone can explain the difference. This may help me identify the issue I am seeing. Steps to reproduce: [jbreitma@host ~]# ls /clients/Client1/tmpint/ oas prodops [jbreitma@host ~]# grep Client1 /etc/mtab Client1-nfs.Client1.blackrock.com:/clients/Client10101/homes1/tmpint /clients/Client1/tmpint nfs rw,hard,intr,addr=1.1.1.1 0 0 [jbreitma@host ~]# grep Client1 /proc/mounts prod-autofs.clients.common /clients/Client1/apps autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/d0/prod1/reports autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/proj/GPA/historical-data autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/proj/pkg_test autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/proj/space autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/tmpint autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/u1/cliops autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/u1/prod/reports autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/usr/local/bfm/std autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/web/htdocs autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 Client1-nfs.Client1.blackrock.com:/clients/Client10101/homes1/tmpint /clients/Client1/tmpint nfs rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retr ans=2,sec=sys,addr=Client1-nfs.Client1.blackrock.com 0 0 [jbreitma@host ~]# umount /clients/Client1/tmpint [jbreitma@host ~]# grep Client1 /etc/mtab [jbreitma@host ~]# [jbreitma@host ~]# grep Client1 /proc/mounts prod-autofs.clients.common /clients/Client1/apps autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/d0/prod1/reports autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/proj/GPA/historical-data autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/proj/pkg_test autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/proj/space autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/tmpint autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/u1/cliops autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/u1/prod/reports autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/usr/local/bfm/std autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 prod-autofs.clients.common /clients/Client1/web/htdocs autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 After some time, Client1 is no longer visible in /proc/mounts. I would be interested to know what is going on, but would settle for a command to run that could provide a consistent answer between /etc/mtab and /proc/mounts. Thanks. Jason Breitman jason.breitman@blackrock.com -----Original Message----- From: Breitman, Jason Sent: Tuesday, November 10, 2009 10:57 AM To: 'Ian Kent' Cc: autofs@linux.kernel.org Subject: RE: [autofs] automount restart required I will give an example of 1 stanza to help provide clarity of the map. /clients/CLIENT1 is the offset Once logged into a host you can cd to /clients/CLIENT1/proj/space /clients/CLIENT1/proj/pkg_test /clients/CLIENT1/proj/GPA/historical-data /clients/CLIENT1/d0/prod1/reports /clients/CLIENT1/u1/prod/reports /clients/CLIENT1/usr/local/bfm/std /clients/CLIENT1/tmpint /clients/CLIENT1/apps /clients/CLIENT1/web/htdocs All mounts are under the offset /clients/CLIENT1. I hope I am clear in my explanation. /etc/auto.master has the below entry /clients prod-autofs.clients.common -hard,intr prod-autofs.clients.common has the below entry Client1 /proj/space Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \ /proj/pkg_test 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 I thought my mistake might have been that /etc/auto.master should look like (indirect vs. direct map) /- prod-autofs.clients.common -hard,intr and prod-autofs.clients.common should look like /clients/Client1 \ /proj/space Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \ /proj/pkg_test 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 Please say if the formatting gets garbled and I will figure out some other way to get you the map entries. Jason Breitman jason.breitman@blackrock.com -----Original Message----- From: Ian Kent [mailto:raven@themaw.net] Sent: Thursday, November 05, 2009 8:50 PM To: Breitman, Jason Cc: autofs@linux.kernel.org Subject: Re: [autofs] automount restart required 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. 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: automount restart required 2009-11-16 3:13 ` Breitman, Jason @ 2009-11-16 8:40 ` Ian Kent 0 siblings, 0 replies; 10+ messages in thread From: Ian Kent @ 2009-11-16 8:40 UTC (permalink / raw) To: Breitman, Jason; +Cc: autofs Breitman, Jason wrote: > It appears that there are a few negatives to using direct maps so I have > been evaluating other options. > You must restart autofs anytime updates are made to the direct > map. Correct. > All entries in the direct map show up in /proc/mounts and I > believe coincide with a mount which will cause a strain on the NFS > Server. (mount storm) Why, they are autofs fs mounts not NFS mounts. They are the triggers that cause a mount to be made, one for each direct mount in the direct map. > > I noticed a difference between /etc/mtab and /proc/mounts and hope > someone can explain the difference. > This may help me identify the issue I am seeing. > > Steps to reproduce: > [jbreitma@host ~]# ls /clients/Client1/tmpint/ > oas prodops > > [jbreitma@host ~]# grep Client1 /etc/mtab > Client1-nfs.Client1.blackrock.com:/clients/Client10101/homes1/tmpint > /clients/Client1/tmpint nfs rw,hard,intr,addr=1.1.1.1 0 0 > > [jbreitma@host ~]# grep Client1 /proc/mounts > prod-autofs.clients.common /clients/Client1/apps autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/d0/prod1/reports autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/proj/GPA/historical-data > autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/proj/pkg_test autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/proj/space autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/tmpint autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/u1/cliops autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/u1/prod/reports autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/usr/local/bfm/std autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/web/htdocs autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > Client1-nfs.Client1.blackrock.com:/clients/Client10101/homes1/tmpint > /clients/Client1/tmpint nfs > rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retr > ans=2,sec=sys,addr=Client1-nfs.Client1.blackrock.com 0 0 > > [jbreitma@host ~]# umount /clients/Client1/tmpint > > [jbreitma@host ~]# grep Client1 /etc/mtab Well, what do you expect! You have manually umounted an autofs managed mount (which isn't really supported, although autofs tries to recover) and mount immediately updates /etc/mtab but /proc/mounts will only be different when the mount has actually gone away within the kernel. > > [jbreitma@host ~]# > > [jbreitma@host ~]# grep Client1 /proc/mounts > prod-autofs.clients.common /clients/Client1/apps autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/d0/prod1/reports autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/proj/GPA/historical-data > autofs rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/proj/pkg_test autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/proj/space autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/tmpint autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/u1/cliops autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/u1/prod/reports autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/usr/local/bfm/std autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > prod-autofs.clients.common /clients/Client1/web/htdocs autofs > rw,fd=59,pgrp=4040,timeout=1800,minproto=5,maxproto=5,offset 0 0 > > > After some time, Client1 is no longer visible in /proc/mounts. > I would be interested to know what is going on, but would settle for a > command to run that could provide a consistent answer between /etc/mtab > and /proc/mounts. The answer is that /proc/mounts is authoritative, it reflects the state of mounts in the kernel, whereas /etc/mtab is a file that is maintained by user space utilities and has a long history of problems. That would be why I've spent so much time to make autofs independent of it. I'm fairly sure your version of autofs on RHEL is recent enough so check your autofs configuration for "USE_MISC_DEVICE" and set it "yes" if it is not already. Then you should do a clean shutdown and start of autofs to make sure you are using the feature and then autofs should not use /etc/mtab. This may be an indication of a problem and needs further investigation. If you don't provide a debug log, as previously requested, then this is going to go nowhere. The debug log is essentially the starting point for problem investigation. That's just the way it is. > > Thanks. > > Jason Breitman > jason.breitman@blackrock.com > > -----Original Message----- > From: Breitman, Jason > Sent: Tuesday, November 10, 2009 10:57 AM > To: 'Ian Kent' > Cc: autofs@linux.kernel.org > Subject: RE: [autofs] automount restart required > > I will give an example of 1 stanza to help provide clarity of the map. > > /clients/CLIENT1 is the offset > > Once logged into a host you can cd to > > /clients/CLIENT1/proj/space > > /clients/CLIENT1/proj/pkg_test > > /clients/CLIENT1/proj/GPA/historical-data > > /clients/CLIENT1/d0/prod1/reports > > /clients/CLIENT1/u1/prod/reports > > /clients/CLIENT1/usr/local/bfm/std > > /clients/CLIENT1/tmpint > > /clients/CLIENT1/apps > > /clients/CLIENT1/web/htdocs > > All mounts are under the offset /clients/CLIENT1. > I hope I am clear in my explanation. > > /etc/auto.master has the below entry > > /clients prod-autofs.clients.common -hard,intr > > prod-autofs.clients.common has the below entry > > Client1 /proj/space > Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \ > /proj/pkg_test > 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 > > I thought my mistake might have been that /etc/auto.master should look > like (indirect vs. direct map) > > /- prod-autofs.clients.common -hard,intr > > and prod-autofs.clients.common should look like > > /clients/Client1 \ > /proj/space > Client1-nfs.Client1.blackrock.com:/clients/Client10103/proj/space \ > /proj/pkg_test > 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 > > Please say if the formatting gets garbled and I will figure out some > other way to get you the map entries. > > > Jason Breitman > jason.breitman@blackrock.com > > -----Original Message----- > From: Ian Kent [mailto:raven@themaw.net] > Sent: Thursday, November 05, 2009 8:50 PM > To: Breitman, Jason > Cc: autofs@linux.kernel.org > Subject: Re: [autofs] automount restart required > > 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. > > > 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. > > _______________________________________________ > autofs mailing list > autofs@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/autofs ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2009-11-16 8:40 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2009-11-10 15:56 ` Breitman, Jason 2009-11-16 3:13 ` Breitman, Jason 2009-11-16 8:40 ` Ian Kent
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.