From: Matthias Koenig <mkoenig@suse.de>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: mtab corruption
Date: Tue, 09 Jan 2007 15:36:45 +0100 [thread overview]
Message-ID: <n7xlkkc4682.fsf@sor.suse.de> (raw)
In-Reply-To: <1167962084.4289.8.camel@raven.themaw.net> (Ian Kent's message of "Fri, 05 Jan 2007 10:54:44 +0900")
Ian Kent <raven@themaw.net> writes:
> On Thu, 2007-01-04 at 09:03 -0800, Jim Carter wrote:
>> On Thu, 4 Jan 2007, Ian Kent wrote:
>> > On Wed, 2007-01-03 at 17:03 +0100, Dieter Stüken wrote:
>> > > I frequently end up with a broken mtab. This results in a message like:
>> > > mount(nfs): warning: /home/stueken is already mounted
>>
>> Sorry, I don't have anything useful to add on the mtab corruption issue.
>> We do a ton of NFS automounting and don't see this issue.
>>
>> > > I'm using a SuSE-10.1 x86_64-smp system with a 2.6.16.21-0.25-smp kernel.
>> > > I upgraded from autofs-4.1.4-23 to autofs-4.1.4-37, but the mtab
>> >
>> > I don't know what this means, I don't use SuSE.
>>
>> The trailing numbers differentiate variants of the "same" software version,
>> e.g. security patches. SuSE has a policy of backporting patches to old
>> versions, if feasible, in contrast to Debian, which I think would send
>> out the latest version including the latest patch. The idea is to minimize
>> feature changes except at distro version transitions.
>
> Sure, but my point was that I'm not familiar with what patches the SuSE
> maintainer may have added. Perhaps this would be a good time for the
> SuSE maintainer to speak up, if present.
Yes, I know about this problem. However I have not had the time yet to do
some further debugging.
We have a patch addressing the mtab locking part of fstab.c however this
seems not to be enough. According to a recent mail on the util-linux-ng list
there is a principal problem with the method used in mount. This needs
some more investigation. As soon this problem is fixed I think this is
important enough to backport.
Matthias
_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
next prev parent reply other threads:[~2007-01-09 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 16:03 mtab corruption Dieter Stüken
2007-01-04 1:34 ` Ian Kent
2007-01-04 17:03 ` Jim Carter
2007-01-05 1:54 ` Ian Kent
2007-01-09 14:36 ` Matthias Koenig [this message]
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=n7xlkkc4682.fsf@sor.suse.de \
--to=mkoenig@suse.de \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/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.