On Fri, 2007-01-26 at 19:10 +0100, Lukas Kolbe wrote: > On Sa, 2007-01-27 at 02:12 +0900, Ian Kent wrote: > > > > In syslog I get random messages like this: > > > Jan 26 16:39:29 demon automount[16757]: mount(generic): warning: > > > /homes/musr657 is already mounted > > > Jan 26 16:39:42 demon automount[17062]: mount(generic): warning: > > > /nfs4homes/musr946 is already mounted > > > for exactly the mountpoints that belong to root afterwards. > > > > Your mtab locking is broken. > > Get a mount(8) that's not broken and then re-evaluate. > > Thanks for the pointer. I found a discussion you were involved in in the > util-linux-ng mailinglist at the beginning of january, is that the > locking you talk about (see > http://www.mail-archive.com/[email protected]/msg00005.html)? > > I'll have a look at it on monday and see if I can patch our mount and if > it makes a difference!
No and yes. This issue has come up fairly often over the last 3-5 years. What I expect when posting a comment like this is that the relevant distribution maintainer speak up and justify that mount(8) in their distribution has been patched to fix this issue. That of course doesn't mean that it isn't still broken but indicates that the right people are aware of the problem, have attempted to fix it, and will help out if needed. All distributions should have something included to fix this by now but it seems that may not be the case. It may be worthwhile looking at http://www.kernel.org/pub/linux/daemons/autofs/v4/autofs-4.1.4-configureable-locking.patch. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
