One of the fields that 'lock_dump' produces is the inode for the file held. I
will often use 'find' and specify the inode number to figure out which file is
locked. You'll probably have to convert the inode number from hex to decimal.
Aaron
--
Aaron Sims
Professional Services Engineer
Network Appliance
aaron.sims(a)netapp.com
404-226-7382 (cell)
408-822-8947 (voice mail)
> -----Original Message-----
> From: Muhlestein, Mark [mailto:mark.muhlestein@netapp.com]
> Sent: Thursday, March 09, 2000 7:04 PM
> To: 'Stephen C. Woods'
> Cc: 'toasters(a)mathworks.com'
> Subject: RE: Filer showing held locks
>
>
> You can use the rc_toggle_basic command lock_dump:
>
> lock_dump -f
> lock_dump -h
>
> -f dumps by file, -h dumps by host.
>
> Mark Muhlestein -- mmm(a)netapp.com
>
> -----Original Message-----
> From: Stephen C. Woods [mailto:scw@seas.ucla.edu]
> Sent: Thursday, March 09, 2000 3:17 PM
> To: toasters(a)mathworks.com
> Subject: Filer showing held locks
>
>
> Is it possable to see file locks on a filer?
> That is to say, 'Is there an equivalent to lslk?'.
>
> -----
> Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095;
> (310)-825-8614
> Finger for public key scw(a)cirrus.seas.ucla.edu,Internet
> mail:scw@SEAS.UCLA.EDU
>