From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: autofs@linux.kernel.org
Subject: kernel panic when accessing local filesystems on NFS server
Date: Wed, 12 Apr 2006 14:48:15 +0200 [thread overview]
Message-ID: <443CF70F.90001@inria.fr> (raw)
Hello.
Since last reboot, I encounter heavy troubles when trying to access
local filesystems also advertised by LDAP as available for auto-mounting.
/etc/fstab:
...
/dev/hdb1 /home/graves/ftp ext3 defaults 1 2
/etc/exports:
...
/home/graves/ftp/pub *.inria.fr(ro,async,all_squash,insecure)
/etc/init.d/autofs status:
...
/usr/sbin/automount --timeout=60 /home/graves ldap
ou=auto.home.graves,ou=autofs,dc=village,dc=inria,dc=fr
LDAP client map:
# auto.home.graves, autofs, village.inria.fr
dn: ou=auto.home.graves,ou=autofs,dc=village,dc=inria,dc=fr
objectClass: top
objectClass: automountMap
ou: auto.home.graves
# /, auto.home.graves, autofs, village.inria.fr
dn: cn=/,ou=auto.home.graves,ou=autofs,dc=village,dc=inria,dc=fr
objectClass: top
objectClass: automount
cn: /
automountInformation: -fstype=nfs,hard,intr graves:/home/graves/&
When autofs is not activated, ls /home/graves/ftp works OK. As soon as
autofs is activated, ls /home/graves/ftp triggers immediate kernel
panics (can't handle kernel paging request). This is happening on a
mandriva 10.2, running kernel 2.6.11-13mdk, with autofs 4.1.4. It is
also a recent problem, which didn't occured earlier.
It seems I have to hide client maps to servers exporting them. Which is
quite difficult as I use LDAP precisely to propagate a centralised
configuration. But even if my configuration is wrong, autofs ought to be
a little more robust here.
next reply other threads:[~2006-04-12 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 12:48 Guillaume Rousse [this message]
2006-04-12 18:20 ` kernel panic when accessing local filesystems on NFS server Jeff Moyer
2006-04-13 12:18 ` Guillaume Rousse
2006-04-13 23:12 ` Jim Carter
2006-04-16 17:29 ` Guillaume Rousse
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=443CF70F.90001@inria.fr \
--to=guillaume.rousse@inria.fr \
--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.