Current 2.6.0 (2.6.0-test5+BK as of 16.09) hangs on df when
the am_utils automounter is in use. It displays hda* partitions and next
by mountpoint list is amd but then df hangs, wchan is rpc_execu*
dmesg only tells
nfs warning: mount version older than kernel
like it always does with current 2.6 kernels for me.
x86, debian unstable.
--
Meelis Roos ([email protected])
>>>>> " " == Meelis Roos <[email protected]> writes:
> Current 2.6.0 (2.6.0-test5+BK as of 16.09) hangs on df when the
> am_utils automounter is in use. It displays hda* partitions and
> next by mountpoint list is amd but then df hangs, wchan is
> rpc_execu*
Please reproduce using ordinary 'mount'...
Cheers,
Trond
On Tue, 16 Sep 2003 17:35:49 +0300 (EEST), Meelis Roos <[email protected]> wrote:
> Current 2.6.0 (2.6.0-test5+BK as of 16.09) hangs on df when
> the am_utils automounter is in use. It displays hda* partitions and next
> by mountpoint list is amd but then df hangs, wchan is rpc_execu*
You're going to have to figure out what amd is doing at that point --
whether it's dead, spinning, waiting for a child process, or something
else. Hanging on df is the expected behavior if amd is not responding to
nfs requests.
Ion
[amd co-maintainer]
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
> > Current 2.6.0 (2.6.0-test5+BK as of 16.09) hangs on df when the
> > am_utils automounter is in use. It displays hda* partitions and
> > next by mountpoint list is amd but then df hangs, wchan is
> > rpc_execu*
>
> Please reproduce using ordinary 'mount'...
Seems that am-utils (or other userland) is at fault - it breaks with
2.4.23-pre4 too...
--
Meelis Roos ([email protected]) http://www.cs.ut.ee/~mroos/
> You're going to have to figure out what amd is doing at that point --
> whether it's dead, spinning, waiting for a child process, or something
> else. Hanging on df is the expected behavior if amd is not responding to
> nfs requests.
It was actually a network configuration problem - I got a wrong IP via
DHCP and changed it to the right one manually. So network was
configured, portmap+amd started, IP address changed from under amd and
then amd hung. Fixing the network configuration made the hang go away so
I will probably not dig into the reasons why amd hangs indefinitely when
the IP chnages.
The kernel is certainly not at fault, it was my bad.
--
Meelis Roos ([email protected])