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. > > > Does your system use mount.nfs from nfs-utils? > > There is an mtab locking error I spotted in nfs-utils recently. > > SuSE 10.1 uses /bin/mount from util-linux-2.12r-35 which does NFS > intrinsically, and not mount.nfs from nfs-utils-1.0.7, which is installed > but minus mount.nfs. OK. So we still don't know if the locking code in util-linux is broken. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
