From: "Latrell" Subject: mount failed: aquire_lock: can't lock lock file interrupted: /var/lock/autofs Date: Thu, 6 Jul 2006 10:17:17 +0800 Message-ID: <004601c6a0a2$5cb575e0$251a17ac@ZyXEL.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5668351386912420074==" Return-path: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org To: autofs@linux.kernel.org This is a multi-part message in MIME format. --===============5668351386912420074== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0041_01C6A0E5.5BD7C4A0" This is a multi-part message in MIME format. ------=_NextPart_000_0041_01C6A0E5.5BD7C4A0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable It seems my post didn't sent. I'm sorry if it's a double post. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Hi All: =20 My scenario is as follows: Use login FTP -> change directory ( autofs = will mount the share in this time) -> access -> logout ( autofs umount = the share ) I keep running the scenario continuously, and I have some observations: 1. One continuous ftp session can operate normally 2. When there are many user sessions run continuous, say 3, the = operation =A1=A7change directory=A1=A8 will fail from time to time. The log message is as follows, the home directory is = /tmp/users/shares/1034(1043): automount[2306]: aquire_lock: can't lock lock file interrupted: = /var/lock/autofs automount[2306]: failed to mount autofs path /tmp/users/shares/1034 automount[2306]: /ramdisk/mnt/var1/tmp/users/shares/1034: mount failed! automount[2298]: aquire_lock: can't lock lock file interrupted: = /var/lock/autofs automount[2298]: failed to mount autofs path /tmp/users/shares/1043 automount[2298]: /ramdisk/mnt/var1/tmp/users/shares/1043: mount failed! =20 I also found the related discussion: http://www.mail-archive.com/autofs@linux.kernel.org/msg05071.html The similarity is I mount and umount frequently in a short time! =20 Is there a patch available for the problem? If not, will the problem be = scheduled in version 5? If not, how can I fix it myself? Can someone advice me? Any advice will be appreciated!~ =20 Thanks in advance, Latrell. ------=_NextPart_000_0041_01C6A0E5.5BD7C4A0 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable

It seems my post didn't=20 sent. I'm sorry if it's a double post.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

Hi All:

 

My scenario is as=20 follows: Use login FTP -> change directory ( autofs will mount the = share in=20 this time) -> access -> logout ( autofs umount the share=20 )

I keep running the=20 scenario continuously, and I have some=20 observations:

1. One continuous ftp=20 session can operate normally

2. When there are many=20 user sessions run continuous, say 3, the operation =A1=A7change=20 directory=A1=A8 will fail = from time to=20 time.

The log message is as=20 follows, the home directory is=20 /tmp/users/shares/1034(1043):

 automount[2306]:=20 aquire_lock: can't lock lock file interrupted:=20 /var/lock/autofs

 automount[2306]:=20 failed to mount = autofs path=20 /tmp/users/shares/1034

 automount[2306]:=20 /ramdisk/mnt/var1/tmp/users/shares/1034: mount=20 failed!

 automount[2298]:=20 aquire_lock: can't lock lock file interrupted:=20 /var/lock/autofs

 automount[2298]:=20 failed to mount=20 autofs path=20 /tmp/users/shares/1043

 automount[2298]:=20 /ramdisk/mnt/var1/tmp/users/shares/1043: mount=20 failed!

 

I also found the=20 related discussion:

http://www.mail-archive.com/autofs@linux.kernel.org/msg05071.html

The similarity is I=20 mount and umount frequently in a short = time!

 

Is there a patch=20 available for the problem? If not, will the problem be scheduled in = version 5?=20  If not, how can I fix it myself?

Can someone advice me?=20 Any advice will be appreciated!~

 

Thanks in=20 advance,

Latrell.

------=_NextPart_000_0041_01C6A0E5.5BD7C4A0-- --===============5668351386912420074== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs --===============5668351386912420074==--