- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: How do I know what is locking a file?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2008 04:16 AM
тАО05-28-2008 04:16 AM
I am receiving the classical error message:
%COPY-E-OPENIN, error opening
disk:[dir]file.log;1 as input
-RMS-E-FLK, file currently locked by another user
The problem is that I have no way to see which process is locking it.
If I execute:
$pipe sh dev/files|sear sys$pipe file
there is no output.
If I enter ANALYZE/SYSTEM and execute:
SDA>show proc/channel all
to an output file, the file doesn't appear.
The system is a two nodes cluster with OpenVMS v8.3.
Is there any other tool to chase the 'ghost' channel?.
Thank you very much in advance.
Regards.
Ana
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2008 04:25 AM
тАО05-28-2008 04:25 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2008 04:26 AM
тАО05-28-2008 04:26 AM
Re: How do I know what is locking a file?
This is how I usually do it
MCR SYSMAN SET ENV/CLUSTER
SYSMAN> PIPE SHOW DEVICE/FILES/NOSYS diskname | SEAR SYS$INPUT: filename
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2008 04:54 AM
тАО05-28-2008 04:54 AM
Re: How do I know what is locking a file?
Thanks for your answers.
Well, I executed the analyze command at the other node but not the 'pipe' command. .
The logs locked are not the original ones. The process is:
.....
original log files copied to [...temporal]*.*.*
(in this case, if the original files are locked, the files are not copied and procedure ends)
.... (some processing not involving these files)
rename [...temporal]*.*.* to [..www]*.*.*
(the rename is ok but, when the procedure is going to copy the [...www]*.*.* to a file, we get the "file currently locked by ...." message.
I think , correct me if I am in a mistake, that, in this case, the other node is not locking the files copied and renamed, because these files has only been used by the procedure.
Anyway, I think you are right that it has something to do with the cluster because this procedure has been working for a long time and, since the moment we add a second node to the cluster and started the web server, the problem is happening some times. Or perhaps it's a chance, I don't know.
I'll execute what you have said the next time I get the error and I'll let you know.
Thanks again.
Ana
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2008 06:16 AM
тАО05-28-2008 06:16 AM
Re: How do I know what is locking a file?
Can you post, on both nodes
$ define show$debug yes
$ sh dev disk
and
$ def show$debug_lckbuf 1
$ sh dev disk
May be you have some dangling locks ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2008 11:08 AM
тАО05-28-2008 11:08 AM
Re: How do I know what is locking a file?
Is it possible that this case is simply a transient conflict; that there are logs or other files or even directory operations involved within these directories, and that by the time you get around to looking, the lock on the log file has been cleared?
I've also seen cases where the batch job log is in the same directory area as the particular batch job operation, and the batch log file itself trips file lock errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2008 12:56 AM
тАО05-29-2008 12:56 AM
Re: How do I know what is locking a file?
Thanks for the commands. I'll test them. Since the moment I wrote this post, the problem has not arisen.
Hoff.
I think you are right because it's something transient.
I haven't told you that the job is a network job and that the copy and rename operations are done by DECnet. This could be the problem if we had a cluster alias defined but, afaik we don't have either defined (at least, I can't see the cluster alias name with NCP>show executor char). Am I right?. Moreover, the second node has no proxy database defined.
As soon as the problem arises again, I'll make a deep research in both nodes with the commands you all have told me, and I'll let you know.
Thanks again
Ana
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2008 04:50 AM
тАО06-02-2008 04:50 AM
Re: How do I know what is locking a file?
The problem has arosen and, in effect, the file is accessed by the other node. It seems that, at the beginning, I didn't do the
suitable tests at the other node.
Now it's my turn to see how to find the reason for it and solve the problem.
Thanks all for your help.
Ana
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2008 04:51 AM
тАО06-02-2008 04:51 AM
Re: How do I know what is locking a file?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2008 05:02 AM
тАО06-02-2008 05:02 AM
Re: How do I know what is locking a file?
To help you, you can try to find the log file opened by any process on a node with a command file (b.com in the following example)
$ ty b.com
$ pipe (wr sys$output "sh proc/id=''pid'/chan") | ana/sys | sea sys$pipe .log
then, if you define a symbol pid
$ pid:==202030F7
$ @b
0050 7FF7E080 81178340 DSA2:[BPFWAR.APP.LOG]BPFWAR_ECHA.LOG;56
$ pid:==2020022E
$ @b
0090 7FF7E100 811186C0 DSA0:[SYS0.SYSEXE]RDMMON.LOG;86
This is not bullet-proof, but it may help