Am Montag, den 29.01.2007, 16:19 +0100 schrieb Lukas Kolbe: > The system is now through more than 25000 mails, and hasn't hit the bug > yet. > When it finished delivering, I'll setup another mailbomb and stress it > over the night, let's cross fingers that it works. I'll then file a bug > with the debian util-linux package and attach the patch to it. > Not close()ing the "we_created_lockfile" in unlock_mtab() seems like a > bug to me, anyway ;)
Okay, the race hit again. Damnit!
Out of about 30000 mails, 8(!!!) didn't get delivered because:
Every 2.0s: ls -al /homes/ /nfs4homes | grep root
Mon Jan 29 16:27:55 2007
drwxr-xr-x 7 root root 0 2007-01-29 16:26 .
drwxr-xr-x 24 root root 4096 2007-01-29 15:26 ..
dr-xr-xr-x 2 root root 0 2007-01-29 16:11 musr352
dr-xr-xr-x 2 root root 0 2007-01-29 16:17 musr847
drwxr-xr-x 8 root root 0 2007-01-29 16:26 .
drwxr-xr-x 24 root root 4096 2007-01-29 15:26 ..
dr-xr-xr-x 2 root root 0 2007-01-29 16:17 musr847
These should look like
drwxr-xr-x 4 musr123 mailtest 4096 2007-01-17 16:59 musr123
And in /var/log/syslog appears again:
Jan 29 16:20:50 demon automount[29640]: mount(generic): warning: /homes/musr352
is already mounted
This was with debian's autofs 4.1.4-13, see
ftp://ftp.de.debian.org/debian/pool/main/a/autofs/
And mount 2.12r-15.1, see ftp://ftp.de.debian.org/debian/pool/main/u/util-linux/
with the attached patch appliend, hence version number -15.1.
So, the patch made the problem appear way less, but it won't go away
completely. Ian, I guess that's what you suspected?
I'll try the test again overnight with an autofs timeout of 300.
--
Lukas
70-mount-fstab-locking.dpatch
Description: application/shellscript
_______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
