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 > > 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.
I don't know what this means, I don't use SuSE. > > 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. This corruption is not actually an autofs problem although verious things have been tried over the years to reduce it. mount(8) is where the problem lies. Does your system use mount.nfs from nfs-utils? There is an mtab locking error I spotted in nfs-utils recently. > > Should I consider to update my kernel, too? Waste of time, nothing to do with the kernel. /etc/mtab is managed entirely by user space code. > > 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? At the moment v5 still expects /etc/mtab to be correct. This can be fairly easily changed but I would prefer to be able to rely on mount(8) because, for large direct mount maps (at least) we will have a performance penalty. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
