Ian Kent <[EMAIL PROTECTED]> 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 [email protected] http://linux.kernel.org/mailman/listinfo/autofs
