[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

460.0. "Mount/foreign shadow disk member get write locked." by HTSC19::KENNETH () Mon Apr 14 1997 06:07

Hi,

One of my customer dismount a shadow set member disk and mount/foreign that 
disk in order to perform an image backup of the disk.

The steps are :

1) dismount the shadow set

2) $ mount/foreign $1$DUA13:
%MOUNT-W-VOLSHDWMEM, mounting a shadow set member volume; volume write locked
%MOUNT-I-MOUNTED, VAXVMSV2055  mounted on _$1$DUA13: (HSJ101)

As shown above, when mount/foreign the disk will get the message above.

The system is running OpenVMS V6.2, however, there is no problem using 
the above method on the pervious version V5.5-2.  

Is there any change on this area?

Finially, the customer use the option /FOREIGN/OVERRIDE=SHADOW_MEMBER instead.

Is it the proper command and just mount/foreign is not support in V6.2 for
this purpose?

Thanks for your help in advance.

Kenneth Leung

T.R	Title	User	Personal Name	Date	Lines
460.1		UTRTSC::utojvdbu1.uto.dec.com::JurVanDerBurg	Change mode to Panic!	`Mon Apr 14 1997 10:12`	5
	How does the customer backup this foreign mounted disk? Normally you mount the disk as a files-11 disk and use backup/image. Jur.
460.2		VMSSG::FRIEDRICHS	Ask me about Young Eagles	`Mon Apr 14 1997 10:54`	11
	Certainly the /over=shadow will tell MOUNT to ignore the shadowing information, and thus the disk will get mounted /write (default). I was not aware that this was a change in behavior.. Is the V6.2 customer running 6.2SSB, or do they have either COMPAT_062 or CLUSIO01_062 (ie, the new MOUNT)?? Thanks, jeff
460.3		EVMS::MORONEY	Hit <CTRL><ALT><DEL> to continue ->	`Mon Apr 14 1997 13:20`	12
	re .0: The behavior you are seeing (writelock the disk unless /OVERRIDE=SHADOW specified) is correct. I didn't know that 5.5-2 was broken regarding this. This behavior prevents someone from dismounting a 2 or 3 member shadowset, mount/foreign (or simply mounting) one of its members, writing to the disk, dismounting it and remounting it into a shadowset. Shadowing wouldn't know that the disks were no longer identical, and this would cause bizarre data corruption problems. -Mike
460.4		AUSS::GARSON	DECcharity Program Office	`Mon Apr 14 1997 22:29`	7
	re .0 Why does the customer care that the disk is mounted writelocked? As .3 points out, any write to the disk could be bad news. In particular if the customer is using BACKUP/RECORD then this is either dangerous or pointless. Without testing it,... MOUNT/NOWRITE/FOREIGN might be a better workaround if they just want to get rid of the error message.