mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Gernoth <simigern@stud.uni-erlangen.de>
To: linux-kernel@vger.kernel.org
Subject: Hanging NFS umounts with 2.4.27
Date: Fri, 5 Nov 2004 11:02:37 +0100	[thread overview]
Message-ID: <20041105100237.GA27689@cip.informatik.uni-erlangen.de> (raw)

Hi,
we have 2 SMP machines running Linux 2.4.27 with autofs which have a high
rate of mounting/umounting. When they are heavily used, it happens that
about once a day a umount-process gets stuck and the only solution is
to reboot the machine.
We can also see this happen (much less often) on our UP workstations,
where in the average only one student is working on a single machine at
a time.

Searching through the Changesets I found 1.1402.1.19:
http://linux.bkbits.net:8080/linux-2.4/cset@1.1402.1.19
After reverting this one, we have a stable umount-behaviour again.

Grepping through the log of the serial console finds the following
hanging umounts (the nfs-servers were up at these moments):
19969 ?        S      9:32 /bin/umount //local/perl-5.004/.arch.os
23437 ?        S      0:00 /bin/umount //local/maple/.arch.os
19969 ?        S      9:40 /bin/umount //local/perl-5.004/.arch.os
23437 ?        S      0:00 /bin/umount //local/maple/.arch.os
19969 ?        S      9:59 /bin/umount //local/perl-5.004/.arch.os
23437 ?        S      0:00 /bin/umount //local/maple/.arch.os
19969 ?        S     10:13 /bin/umount //local/perl-5.004/.arch.os
23437 ?        S      0:00 /bin/umount //local/maple/.arch.os
22491 ?        S      0:00 /bin/umount //local/gnu-utils-1.0/.arch.os
23560 ?        S      0:00 /bin/umount //proj/cipadm

The file-systems are mounted from a Solaris 9 machine with the following
options on the client-side:
rw,nosuid,nodev,retry=5,intr,rsize=8192,noquota,wsize=8192,hard,tcp,addr=...

We are running Debian/Testing with autofs version 4.1.3.

Our current Kernel-config is at:
http://wwwcip.informatik.uni-erlangen.de/~simigern/cip-generic-config
(This Kernel is patched with ACLs and the current autofs-patch, but the
 behaviour can be reproduced with a vanilla kernel.org kernel)

Regards,
  Michael

Please CC me on replies, as I am not subscribed to linux-kernel. Thanks.

-- 
Michael Gernoth                            Department of Computer Science IV 
Martensstrasse 1  D-91058 Erlangen Germany  University of Erlangen-Nuremberg
	         http://wwwcip.informatik.uni-erlangen.de/

             reply	other threads:[~2004-11-05 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 10:02 Michael Gernoth [this message]
2004-11-05 19:55 ` Trond Myklebust
2004-11-05 20:22   ` Michael Gernoth
2004-11-08 21:21   ` Michael Gernoth

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=20041105100237.GA27689@cip.informatik.uni-erlangen.de \
    --to=simigern@stud.uni-erlangen.de \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®