From: Greg Rudd (g.rudd@isu.usyd.edu.au)
Date: Mon Jan 20 2003 - 20:03:00 EST
Thanks to Johan Brusche and Pat O'Brien for their help.
The solution to the problem was found by moving the advfs domains off dsk10
and then zeroing the existing disk label and writing a new disk label to
dsk10. Then I added a partition of dsk10 into the rootdg group and then
removed from the group. Which showed the same info with the voldisk list
command as with other disks that are not in the LSM config. After this I
tried to execute the volsave command, which then completed sucessfully. The
only thing I can think that caused this problem that the lsm config must have
got screwed up after the upgrade from 4.0G to 5.1A
-greg
On Monday 20 January 2003 18:43, Greg Rudd wrote:
> Hi all
>
>
> I am having a problem when trying to save the lsm configuration on my
> machine by typing volsave but I am getting the following error.
>
> LSM configuration being saved to
> /usr/var/lsm/db/LSM.20030120183500.tiberius
>
> Disk dsk10 is in error state. Not saving configuration for dsk10.
>
> LSM Configuration saved successfully to
> /usr/var/lsm/db/LSM.20030120183500.tiberius
>
> I have checked the configuration and dsk10 is not alocated into any lsm
> disk group but has a advfs filedomain on it.
>
> Also I note that in the new lsmsa java application you can only mirror
> volumes in it but you can not remove mirrors but however in the old dxlsm
> application you can do this without any problem.
>
>
> OS tru64 5.1a connected to a hsz70 raid controller.
>
> Any Ideas as to what has gone wrong here
>
> Thanks in advance. -greg
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:04 EDT