PROBLEM
Jan 28 ... automountd[168]: dev 800140, rdev 2740262: not in mnttab
Jan 28 ... automountd[168]: dev 800140, rdev 27401cf: not in mnttab
FIX
My customer rebooted the machine.
RESPONSES
James Hsieh has the most informative response. He asks that I
look for duplicate mounts and then
log off users that own those directories
umount the offending directories.
James' advice seems right because the most likely cause is automounted
home directories.
jacques.rall identified a new source of information.
search for 'mnttab' at: http://www.dataman.nl/cgi-bin/sunmanagers
greg
_______________________________________________________________
Greg Polanski greg_polanski@adc.com
ADC Telecommunications
MS 254 612-946-2270
4900 West 78-th St 612-946-3910 FAX
Bloomington, MN 55435 612-580-6873 Pager
_______________________________________________________________
____________________________________________________________
>From jhsieh@soe.ucsd.edu Tue Jan 28 16:36:32 1997
After our machines have been up for some time, our main S1000 develops a
similar problem. The problem appears to be automounter losing track of
what it's really automounting.
Do a df | sort on your affected machine. You'll notice that there are
probably directories mounted twice. That's the cause of your problem.
automount has lost track of its mounts and somehow mounted some things
twice. And best as I can tell, while trying to unmount one partition,
it somehow gets the other and gets confused and thus you get those
messages.
Try doing a "umount" of all the duplicate mounts. It's best if you log the
affected users off and kill all their processes completely -- then you should
be able to unmount both instantiations. Otherwise, you'll likely only get
on instantiation, and probably, the wrong one to clear the error message.
If you can get these duplicate mounted directories cleared, your messages
should stop.
It's interesting that kernel patch 41 didn't fix this -- I thought it would
have...we haven't gotten there yet and at this point, I'm just waiting for
2.6 and going to go from 2.4 to 2.6 all at once.
Good luck.
--James
-- [ James Hsieh O Programmer, School of Engineering ] [ UC San Diego --+-- Office of Engineering Computing ] [ 9500 Gilman Dr 0405 | email: jhsieh@soe.ucsd.edu ] [ La Jolla, CA 92093-0405 / \ http://www-soe.ucsd.edu/personal/jhsieh ]____________________________________________________________
>From jacques.rall@za.eds.com Wed Jan 29 03:31:48 1997
search for 'mnttab' at: http://www.dataman.nl/cgi-bin/sunmanagers ____________________________________________________________
>From Anthony.Worrall@reading.ac.uk Tue Jan 28 09:25:25 1997
If this a cdrom with a hsfs being loopback mounted then it should be fixed in the next (45) release of the 101945 kernal jumbo patch.
I hope this helps
(Greg P.: It is not a CD. The files are automounted home directories. ) ____________________________________________________________
>From vaughn@cbis.ece.drexel.edu Tue Jan 28 12:47:43 1997
I had the same problem a couple weeks ago. I was able to solve the problem without rebooting.
I stopped autofs in /etc/init.d. I created an entry in /etc/mnttab ran umount as root. I think I had to wait about 5 minutes before it would let me umount (even without automountd running). ____________________________________________________________
>From Matthew.Stier@mci.com Tue Jan 28 12:53:39 1997
Rebooting is the fix for the symptom.
The cure is to find out why mounted files are (getting purged from / never getting written in) the mnttab file.
The automounter will also spew these messages is there is an error in the automount maps. (Including trailing spaces)
____________________________________________________________
> From sun-managers-relay@ra.mcs.anl.gov Tue Jan 28 08:59:46 1997 > To: sun-managers@eecs.nwu.edu > Subject: automountd dev ... rdev ...: not in mnttab > > What is the best cure for this problem? > > I am going to recommend rebooting, when convenient. Tech support has > also recommended rebooting. I did not find anything in the FAQ. > I did not recognize an answer in the Solaris System Admin Answerbook. > > The system is Solaris with recent recommended patches. > SunOS nelogix 5.4 Generic_101945-41 sun4d sparc > > I have killed and restarted the automounter. The command, 'automount' > does not appear to have an effect. > > Thanks > > greg > > > Jan 28 09:53:16 nelogix automountd[168]: dev 800140, rdev 2740262: not in mnttab > Jan 28 09:53:18 nelogix automountd[168]: dev 800140, rdev 27401cf: not in mnttab > Jan 28 09:53:18 nelogix automountd[168]: dev 800140, rdev 2740264: not in mnttab > > # /etc/init.d/autofs stop > umount: /home busy > # /etc/init.d/autofs start > > Jan 28 10:01:38 nelogix automountd[3964]: dev 800140, rdev 274022f: not in > mnttab > Jan 28 10:01:38 nelogix automountd[3964]: dev 800140, rdev 2740260: not in > mnttab > Jan 28 10:01:41 nelogix automountd[3964]: dev 800140, rdev 2740262: not in > mnttab > Jan 28 10:01:44 nelogix automountd[3964]: dev 800140, rdev 27401cf: not in > mnttab > Jan 28 10:01:45 nelogix automountd[3964]: dev 800140, rdev 2740264: not in > mnttab > > > _______________________________________________________________ > Greg Polanski greg_polanski@adc.com > ADC Telecommunications > MS 254 612-946-2270 > 4900 West 78-th St 612-946-3910 FAX > Bloomington, MN 55435 612-580-6873 Pager > _______________________________________________________________ > >
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:43 CDT