"volume is write locked" why?

[Gilles Pion]

Hello everybody,

Does someone have any idea on what is happenning here:

$ mount $1$dga140 DB /over=shadow
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, DB mounted on _$1$DGA140:

But:
$ mount $1$dga140 DB /over=shadow/foreign
%MOUNT-I-MOUNTED, DB mounted on _$1$DGA140:

And:
$ mount $1$dga140 DB
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, DB mounted on _$1$DGA140:


Why VMS does not honour the "/over=shadow" argument when mounting a volume in "normal" mode (should not be write locked) but accept it with /foreign? (volume is mounted read/write in this case)

[Karl Rohwedder]

< $ mount $1$dga140 DB /over=shadow
< %MOUNT-I-WRITELOCK, volume is write locked
< %MOUNT-I-MOUNTED, DB mounted on _$1$DGA140:

I think VMS honors the /OVER=SHAD, because otherwise it would have told you, that it mounts a former shadowset member.

So the write-lock is caused by something else. Are any errors logged? How does the volume protection looks like and the protection of the .SYS files in the MFD?

regards Kalle

[Ian Miller. · Accepted solution]

check the volume structure with ANALYZE/DISK or DFU and check for device errors.

[Gilles Pion]

I've forgot to try the 4th combination of qualifiers ("/foreign" without "/over=shadow")

in this case the VOLSHDWMEM warning is issued, why only when using "/foreign"?

$ mount $1$dga140 DB /for
%MOUNT-W-VOLSHDWMEM, mounting a shadow set member volume; volume write locked

[Gilles Pion]

>check the volume structure with ANALYZE/DISK
>or DFU and check for device errors.

Already done, found only "normal" errors on a snapshot volume (like DELHEADER_BUSY, HEADER_DEL, etc...)

But I've just noticed some "hard" errors on thet volume,
I've informed the support.

Thanks to all

[Wim Van den Wyngaert]

Just wondering : why did mount give you informationals while you had device errors ?
Is seems that it decided on itself to add /nowrite ? Could this happen to my disks too without an error being reported to DCL ?

Wim