From: "Dieter Stüken" <stueken@conterra.de>
To: autofs@linux.kernel.org
Subject: mtab corruption
Date: Wed, 03 Jan 2007 17:03:21 +0100 [thread overview]
Message-ID: <459BD3C9.9090201@conterra.de> (raw)
I frequently end up with a broken mtab. This results in a message like:
mount(nfs): warning: /home/stueken is already mounted
I'm using a SuSE-10.1 x86_64-smp system with a 2.6.16.21-0.25-smp kernel.
After I read about new patches to solve some mtab locking problems
I upgraded from autofs-4.1.4-23 to autofs-4.1.4-37, but the mtab
corruption still occurs.
Seems the problem became even worse since a mount request sometimes
takes about 5 seconds (due to some LDAP configuration problems) while
a bunch of other mount requests are coming in.
In addition this is an SMP system.
Should I consider to update my kernel, too?
Unfortunately I could not convince my sysads to do so, as they are
afraid of even more problems with newer kernels...
I noticed the upcoming autofs5. Should I wait for it?
thanks for advice,
- Dieter.
next reply other threads:[~2007-01-03 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 16:03 Dieter Stüken [this message]
2007-01-04 1:34 ` mtab corruption Ian Kent
2007-01-04 17:03 ` Jim Carter
2007-01-05 1:54 ` Ian Kent
2007-01-09 14:36 ` Matthias Koenig
2007-01-09 15:02 ` Ian Kent
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=459BD3C9.9090201@conterra.de \
--to=stueken@conterra.de \
--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.