[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: RedHat ES4 boot hangs mounting NFS filesystems
- From: "Collins, Kevin (MindWorks)" <KCollins chevron com>
- To: "Red Hat Enterprise Linux 4 (Nahant) Discussion List" <nahant-list redhat com>
- Cc: ldap-interop fini net
- Subject: RE: RedHat ES4 boot hangs mounting NFS filesystems
- Date: Wed, 13 Jul 2005 10:12:20 -0700
Title: RedHat ES4 boot hangs mounting NFS filesystems
Just as a follow up, I narrowed this problem down to
specifically the mount command. After running 'strace mount' I realized it was
hanging on a futex() call (with FUTEX_WAIT). Some Google searching turned up
very similar bugs in RH9 (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90036),
but in that case it was with smbfs mounts (also handled by the netfs rc
script).
I'm now trying to identify if there is already a bug
submitted for this against ES4, but my bugzilla kung-fu is not strong :)
Anyone else experienced this problem or seen this bug reported? If not, I'll
report it myself.
The listed workaround of setting LD_ASSUME_KERNEL to a
non-NPTL kernel version works, but I would like to get the bug
fixed.
Thanks,
Kevin
Hi,
I
converted a RedHat ES4 system to use LDAP (it was previously using NIS)
yesterday. Now, when I attempt a boot, the system hangs at "Mounting NFS
Filesystems" (part of the /etc/init.d/netfs rc script). I have an ES3 system
configured the same and it works fine.
I have narrowed the problem down to using LDAP for
hostname resolution in /etc/nsswitch.conf:
hosts: files ldap
dns
The NFS host (one server for all mounts in question)
is in both LDAP and DNS. If I attempt booting with this configuration the system
hangs trying to mount NFS filesystems.
Any of the following fix the problem:
1) add the host in question to /etc/hosts
2) put dns before ldap in nsswitch.conf
3) change /etc/fstab to use the IP address of the
NFS server
If I boot to runlevel 2 (before NFS mounts occur), I
can login and run 'getent' successfully and it immediately returns the
information from LDAP (I can tell because LDAP has aliases and DNS doesn't). If
I then try an init to runlevel 3 or 5, it hangs at the NFS mount
step.
Does anyone have any ideas? I can't put DNS ahead of
LDAP in the search order because DNS is outside my group's control and we need
to have changes available at near-realtime.
I've carbon-copied the LDAP Interop list as well,
hoping someone can help.
Thanks,
Kevin
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]