I dug into it a bit.....It appears that autofs believes I am running a
different kernel than the directory structure in /lib/modules would
indicate
>From /var/log/messages
Dec 20 13:52:58 ingram automount[8924]: >> mount: fs type autofs not
supported by kernel
Dec 20 13:52:58 ingram automount[8924]: failed to mount autofs path
/clamscan/vadnais/rootdir
Dec 20 13:52:58 ingram automount[8924]: /clamscan/vadnais/rootdir: mount
failed!
Dec 20 13:52:59 ingram modprobe: FATAL: Could not load
/lib/modules/2.6.5-7.202.7-default/modules.dep: No such file or directory
Originally I didn't connect the modprobe error as being part of the
problem. But when I created a symbolic link for 2.6.5-7.202.7-default in
the /lib/modules directory pointing back to 2.6.5-7.191-default it made
things work, but I know that's the wrong way to do this.
drwxr-xr-x 6 root root 4096 Dec 20 15:14 ./
drwxr-xr-x 13 root root 4096 Dec 20 13:50 ../
drwxr-xr-x 5 root root 4096 Dec 20 15:13 2.6.5-7.191-default/
lrwxrwxrwx 1 root root 19 Dec 20 15:14 2.6.5-7.202.7-default ->
2.6.5-7.191-default/
drwxr-xr-x 2 root root 4096 Jun 28 13:41 2.6.5-override-default/
drwxr-xr-x 3 root root 4096 Dec 20 13:49 precompiled/
drwxr-xr-x 3 root root 4096 Jun 28 13:41 scripts/
osrelease entry in /proc/sys/kernel says:
ingram:/ # cat /proc/sys/kernel/osrelease
2.6.5-7.191-default
So clearly linux thinks I'm runing 191-default not 202-default. So why
would autofs stuff be looking for 202-default tree in /lib/modules?
So the question really becomes why did the SP-2 update leave me in this
state? Interestingly enough, prior to the update of SP2 I there was similar
stuff happening, it was trying to access a different dir in /lib/modules. I
don't know what the installed kernel level was at that time.
Dec 19 15:45:01 ingram modprobe: FATAL: Could not load
/lib/modules/2.6.5-7.97-default/modules.dep: No such file or directory
Dec 19 15:45:01 ingram last message repeated 2 times
Dec 19 15:45:01 ingram automount[13973]: >> mount: fs type autofs not
supported by kernel
Dec 19 15:45:01 ingram automount[13973]: /clamscan/vadnais/rootdir: mount
failed!
Dec 19 15:45:01 ingram automount[13976]: >> mount: fs type autofs not
supported by kernel
Dec 19 15:45:01 ingram automount[13976]: /clamscan/vadnais/boot: mount
failed!
Mark Post
<[EMAIL PROTECTED]
et> To
Sent by: Linux on [email protected]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: SLES 9 SP2 on Intel - Does that
include an autofs aware kernel?
12/20/2005 02:58
PM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
According to /usr/src/linux/Configure.help, if the support was built as a
module, it should be named autofs.o/autofs.ko. Try doing a "modprobe
autofs" and see what happens.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
James Melin
Sent: Tuesday, December 20, 2005 10:24 AM
To: [email protected]
Subject: SLES 9 SP2 on Intel - Does that include an autofs aware kernel?
I went through all the motions of installing the base SLES9 system onto
intel hardware but there was a problem on the portal for me getting
maintenance. That's been resolved, and I'm downloading it now. Just that
hte kernel that is running on the x86 machine is reporting autofs not
supported by the currently running kernel.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
