HI all
I failed to add the following info:
voldisk list dsk10
Device: dsk10
devicetag: dsk10
type: sliced
flags: online error autoconfig
errno: Device path not valid
volprint -g rootdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg rootdg rootdg - - - - - -
dm dsk9h dsk9h - 29696 - - - -
dm dsk19h dsk19h - 3072 - - - -
volprint -g fin |more
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
PUTIL0
dg fin fin - - - - - -
dm dsk20a dsk20a - 36859904 - - - -
dm rzc26c dsk13c - 88864291 - - - -
dm rzd26c dsk14c - 88866466 - - - -
dm rzf26b dsk16b - 44427811 - - - -
dm rzg26b dsk17b - 30718976 - - - -
dm rzh26c dsk18c - 88866466 - - - -
dm rz26c dsk11c - 88864291 - - - -
dm rz27b dsk19b - 44423715 - - - -
Hope this helps
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
Received on Mon Jan 20 2003 - 09:43:19 NZDT