I am running Linux client (2.4.20 + NFS-ALL) mounting NetApp filer
(DataOnTap 6.4).
sometime I see lock which are not associated whit a process !
ie: on the filer i do a lock_dump -h : get list of lock
on the client, I match the pid's form the list if my running pid's... and
some are not found, even in the /proc/locks !!!
if I clear the locks on the filer (by a sm_mon -l) they are all claimed !
but after some time (a couple of hours !) a new sm_mon -l clear these locks
!!!!
did someone have ideas ?
thanks
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Having investigate more, I know see that sometimes 2 process are able =
to
obtain the same file lock !
in this case the 2 processes have 10 minutes interval of start ! and =
the
last one is the one in the filer lock table !! not the first !!!
any ideas ?
> -----Original Message-----
> From: Brasseur Val=E9ry=20
> Sent: Wednesday, June 18, 2003 3:13 PM
> To: [email protected]
> Subject: [NFS] strange lock problem
>=20
>=20
> I am running Linux client (2.4.20 + NFS-ALL) mounting NetApp filer
> (DataOnTap 6.4).
>=20
> sometime I see lock which are not associated whit a process !
>=20
> ie: on the filer i do a lock_dump -h : get list of lock
>=20
> on the client, I match the pid's form the list if my running=20
> pid's... and
> some are not found, even in the /proc/locks !!!
>=20
>=20
> if I clear the locks on the filer (by a sm_mon -l) they are=20
> all claimed !
>=20
>=20
> but after some time (a couple of hours !) a new sm_mon -l=20
> clear these locks
> !!!!
>=20
>=20
> did someone have ideas ?
>=20
> thanks=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU=20
> Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly=20
> Commission!
> INetU Dedicated Managed Hosting =
http://www.inetu.net/partner/index.php
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>=20
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
>>>>> " " =3D=3D Brasseur Val=E9ry <[email protected]> writes:
> Having investigate more, I know see that sometimes 2 process
> are able to obtain the same file lock !
If the rpc.statd monitoring is screwing with the filer (telling it
that the client has rebooted and that it must release all locks), then
this is indeed possible.
Is some process on the client perhaps restarting rpc.statd?
Cheers,
Trond
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
> -----Original Message-----
> From: Trond Myklebust [mailto:[email protected]]
> Sent: Thursday, June 19, 2003 7:20 PM
> To: Brasseur Val=E9ry
> Cc: [email protected]; 'Lever, Charles'
> Subject: Re: [NFS] strange lock problem
>=20
>=20
> >>>>> " " =3D=3D Brasseur Val=E9ry <[email protected]> =
writes:
>=20
> > Having investigate more, I know see that sometimes 2 process
> > are able to obtain the same file lock !
>=20
> If the rpc.statd monitoring is screwing with the filer (telling it
> that the client has rebooted and that it must release all locks), =
then
> this is indeed possible.
>=20
> Is some process on the client perhaps restarting rpc.statd?
no I have no process on the client which monitor/restart the rpc.statd =
!
how can track this ?
thanks=20
valery
>=20
> Cheers,
> Trond
>=20
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs