1 INFO-VAX	Mon, 11 Dec 2006	Volume 2006 : Issue 680       Contents: Re: Bad Shadow set member  Re: Bad Shadow set member  Re: Bad Shadow set member   F ----------------------------------------------------------------------    Date: 10 Dec 2006 13:49:51 -0800$ From: "AEF" <spamsink2001@yahoo.com>" Subject: Re: Bad Shadow set memberB Message-ID: <1165787391.511476.78810@j72g2000cwa.googlegroups.com>   Tom Linden wrote: K > following a power outage one of the shadow sets did not mount.  Turns one 2 > of the two members, $42$DKA1200:,  had gone bad. >  > This is in the startup	 > $ MOUNT J > DSA0:/CLUSTER/NOASSIST/INCLUDE/NOCOPY/SHADOW=($42$DKA1200:,$42$DKA1300:) > COMMON >  > 7 > So I had to manually mount omitting the first member.  > H > Doesn't mount detect that one member is bad and mount the other?  Am I > missing a  > qualifier?  = I'm still not sure why this didn't work. If I have time I can 0 experiment with my test system at work tomorrow.  C But, I don't think you're using /INCLUDE the way it was meant to be B used. My impression is that with /INCLUDE you should specify fewerE disks than the entire shadow set. MOUNT then looks at the disk(s) you D specify and determines if any others were in the shadow set the lastD time it was up. So you have to pick a "master disk" and specify justE that one (or up to two for a 3-member set). This way, if both members C were present and mounted before the crash or shutdown, both will be F mounted. But if before the crash or shutdown you removed a member for,D say, an offline backup, only the "master disk" will be mounted. So IG think you don't really want or need /INCLUDE in your case, i.e., if you E are already specifying all the members of the set. I mean, what's the ! point then of including /INCLUDE?    AEF    ------------------------------  % Date: Sun, 10 Dec 2006 14:47:47 -0800 * From: "Tom Linden" <tom@kednos-remove.com>" Subject: Re: Bad Shadow set member) Message-ID: <op.tkc79xsitte90l@hyrrokkin>   G On Sun, 10 Dec 2006 13:49:51 -0800, AEF <spamsink2001@yahoo.com> wrote:    > Tom Linden wrote: I >> following a power outage one of the shadow sets did not mount.  Turns=    =    >> one3 >> of the two members, $42$DKA1200:,  had gone bad.  >> >> This is in the startup 
 >> $ MOUNTI >> DSA0:/CLUSTER/NOASSIST/INCLUDE/NOCOPY/SHADOW=3D($42$DKA1200:,$42$DKA1=  300:) 	 >> COMMON  >> >>8 >> So I had to manually mount omitting the first member. >>I >> Doesn't mount detect that one member is bad and mount the other?  Am =  I  >> missing a
 >> qualifier?  > ? > I'm still not sure why this didn't work. If I have time I can 2 > experiment with my test system at work tomorrow. > E > But, I don't think you're using /INCLUDE the way it was meant to be D > used. My impression is that with /INCLUDE you should specify fewerG > disks than the entire shadow set. MOUNT then looks at the disk(s) you F > specify and determines if any others were in the shadow set the lastF > time it was up. So you have to pick a "master disk" and specify justG > that one (or up to two for a 3-member set). This way, if both members E > were present and mounted before the crash or shutdown, both will be I > mounted. But if before the crash or shutdown you removed a member for,=   F > say, an offline backup, only the "master disk" will be mounted. So II > think you don't really want or need /INCLUDE in your case, i.e., if yo=  u G > are already specifying all the members of the set. I mean, what's the # > point then of including /INCLUDE?   > If you have a two member set, then it is the luck of the draw.  I What I would like is to tell VMS I have a two member set, and mount them=   E both, but if one is bad, mount the good one, and give me diagnostics.  >  > AEF  >        -- =  E Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    ------------------------------    Date: 10 Dec 2006 17:27:09 -0800$ From: "AEF" <spamsink2001@yahoo.com>" Subject: Re: Bad Shadow set memberB Message-ID: <1165800429.856768.316720@79g2000cws.googlegroups.com>   Tom Linden wrote: I > On Sun, 10 Dec 2006 13:49:51 -0800, AEF <spamsink2001@yahoo.com> wrote:  >  > > Tom Linden wrote: J > >> following a power outage one of the shadow sets did not mount.  Turns > >> one5 > >> of the two members, $42$DKA1200:,  had gone bad.  > >> > >> This is in the startup  > >> $ MOUNTM > >> DSA0:/CLUSTER/NOASSIST/INCLUDE/NOCOPY/SHADOW=($42$DKA1200:,$42$DKA1300:)  > >> COMMON  > >> > >>: > >> So I had to manually mount omitting the first member. > >>K > >> Doesn't mount detect that one member is bad and mount the other?  Am I  > >> missing a > >> qualifier?  > > A > > I'm still not sure why this didn't work. If I have time I can 4 > > experiment with my test system at work tomorrow. > > G > > But, I don't think you're using /INCLUDE the way it was meant to be F > > used. My impression is that with /INCLUDE you should specify fewerI > > disks than the entire shadow set. MOUNT then looks at the disk(s) you H > > specify and determines if any others were in the shadow set the lastH > > time it was up. So you have to pick a "master disk" and specify justI > > that one (or up to two for a 3-member set). This way, if both members G > > were present and mounted before the crash or shutdown, both will be J > > mounted. But if before the crash or shutdown you removed a member for,H > > say, an offline backup, only the "master disk" will be mounted. So IK > > think you don't really want or need /INCLUDE in your case, i.e., if you I > > are already specifying all the members of the set. I mean, what's the % > > point then of including /INCLUDE?  > @ > If you have a two member set, then it is the luck of the draw. > J > What I would like is to tell VMS I have a two member set, and mount themG > both, but if one is bad, mount the good one, and give me diagnostics.  > >  > > AEF  [...] G > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    I think what you want is  	 $ MOUNT - ; DSA0:/CLUSTER/NOASSIST/SHADOW=($42$DKA1200:,$42$DKA1300:) -  COMMON  D I think you definitely should drop /INCLUDE. You probably don't wantG /NOCOPY. Using /NOCOPY will be more likely to not mount and less likely & to lose data due to various scenarios.  7 VolShad experts are welcome to chime in and correct me.    AEF    ------------------------------   End of INFO-VAX 2006.680 ************************