SUMMARY: LSM and V4 vs V5

From: Sean McInerney <seanm_at_sybase.com>
Date: Fri, 02 Feb 2001 14:51:49 -0500

 Dear True-64 Managers,

 Thanks for all the replies.

 It would appear the the changes that a V5.1 upgrade performs on
your LSM volume metadata is a one way street. Unless of course
you have done some extra planning with the "volsave" and
"volrestore" commands. It is possible to go back, but it is a
little messy. I have resorted to dividing the volumes depending
on the OS. For the limited time that the 8400 needs to run V4
and V5 for testing product, it is a workable solution.

Regards,
....Sean
 

-- 
Sean P. McInerney, Staff SA 
Sybase Inc.
561 Virginia Road
Concord, MA 01742
seanm_at_sybase.com
978-287-1668
On Wednesday I asked:
>  Dear True64 Managers,
> 
>  Turbolaser running 4.0E, 4.0F and 5.0A (multiboot)
>  Uses LSM for volume management (non root devices)
> 
>  I want to upgrade 5.0A to 5.1.  But I want to be able to use the
> same LSM volumes under 4.0x boxes that I use under 5.x like I
> used to (i.e. 4.0A,B,D,E,F).
> 
>  Have any of you successfully upgraded a 4.0x or 5.0A to 5.1 with
> LSM volumes _and_ then booted back to 4.0E (as in a dual booted
> system) and used the same LSM volumes?
> 
>  5.x seems to have modified some metadata on the LSM volumes that
> 4.0x does not understand.
> LSM doc talks about this but falls short of how to deal with it.
> 
> 
> # voldctl enable
> voldctl: enable failed: Error in disk group configuration copies

Received on Fri Feb 02 2001 - 19:53:31 NZDT