Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

trace open files, problems dismounting volume

 
SOLVED
Go to solution
Larry Bohan
Advisor

trace open files, problems dismounting volume

not-clustered, Alpha vms 8.3, all recent patches

I've got a volume, that I cannot dismount.
(show device/files gives no useful info)

$ dism lda20:
%DISM-W-CANNOTDMT, LDA20: cannot be dismounted
%DISM-W-INSTIMAGE, 2 images installed on volume

$ sh dev/files lda20:
Files accessed on device $1$LDA20: (node) on 8-FEB-2010 12:33:40.55
Process name PID File name
00000000 [000000]INDEXF.SYS;1

No swap/pagefiles on this volume;
normally any open files might be handful of installed images.

I looked at the SDA, (show proc/chan) for
each/every PID. and none showed any channels to LDA20.

I'm about to give up, and just reboot this system later today. But for future reference, can anyone here think of other things to try?
eg. looking at the XQP and/or RMS locks associated with this volume?

(iirc, there was an SDA extension that might help with that ...)
5 REPLIES
EdgarZamora
Trusted Contributor

Re: trace open files, problems dismounting volume

Did you do a $ INSTALL LIST yet?
John Gillings
Honored Contributor

Re: trace open files, problems dismounting volume

Larry,

There's an SDA extension for tracking global sections, but I think you're looking at a bug. I'd expect installed images to show up on SHOW DEVICE/FILES.

Over the years INSTALL has improved greatly in cleaning up after itself, but I'm not sure it will ever reach 100%. I think you've found some obscure sequence of events that after removing the installed images, there's still just enough junk left around that DISMOUNT thinks there are installed images present.

You probably have to reboot, but please consider forcing a crash and sending the dump to HP so they can figure out what's wrong with LDA20.
A crucible of informative mistakes
H.Becker
Honored Contributor
Solution

Re: trace open files, problems dismounting volume

Smells like a feature. :-)

You may have a file (any, no image required) installed (without /open or /anything). Then you can't dismount the volume and can't see it with anything else than INSTALL LIST:

$ install add BREZN$DKC400:[HARTMUT]GZIP.EXE
$ install list BREZN$DKC400:[HARTMUT]GZIP.EXE

DISK$VMS_073:.EXE
GZIP;1
$ sh dev/file BREZN$DKC400:

Files accessed on device BREZN$DKC400: on 8-FEB-2010 22:58:13.97

Process name PID File name
00000000 [000000]INDEXF.SYS;1
$ dism BREZN$DKC400:
%DISM-W-CANNOTDMT, BREZN$DKC400: cannot be dismounted
%DISM-W-INSTIMAGE, 1 image installed on volume
$

As can be seen, the logical name is shown by install, so a search in INSTALL LIST's output for my DKC400 will not show this installed image.

Obviously there are no channels open and there are no global sections for this file.
Larry Bohan
Advisor

Re: trace open files, problems dismounting volume


All 3 of you helped me resolve a brain-cramp,
and recover lost-knowledge.

Looking back, I was using a symbol/shortcut, for install, which included the /global qualifier. (What I would usually be looking
for, is global sects, perhaps with delete-pending...)

It took the extra nudge(s), to go back and
do a unqualified INSTALL LIST.

Thanks.
Hein van den Heuvel
Honored Contributor

Re: trace open files, problems dismounting volume

Larry,

Appreciate the specific feedback. Excelent.

Now that you've been here a little while, please consider given a reply feedback with the 'point' system. Should be easy enough here, as everyone gave great help!

http://forums13.itrc.hp.com/service/forums/helptips.do?#28

Cheers,
Hein