Dear admins,
here is one for the LSM gurus out there:
We had a system running DU4.0b that has been updated from DU3.2. To enlarge the existend / and /usr-Patritions, I booted from CD (4.0B), did the partitioning and restored the data. Then volencap was neccessary to put / and /usr under LSM again.
Now the problem:
We had a diskgroup (t20dg) based on some raidsets. With the enlarged filesystems I am not able to import that diskgroup.
I run volsave every night so I know what the config was:
# DEVICE DISK TYPE GROUP PRIVLEN NCONFIG CONFIGLEN NLOG LOGLEN PUBLEN PUBPATH SYSTEMDISK
re0 t20dg01 sliced t20dg 512 1 347 1 52 25134576 /dev/re0g NO
re1 t20dg02 sliced t20dg 512 2 173 2 26 25134576 /dev/re1h NO
re2 t20dg03 sliced t20dg 512 1 347 1 52 25134576 /dev/re2h NO
re3 re3 sliced t20dg 512 1 347 1 52 25134576 /dev/re3h NO
re4 re4 sliced t20dg 512 1 347 1 52 25134576 /dev/re4h NO
re5 re5 sliced t20dg 512 1 347 1 52 12330480 /dev/re5h NO
rz1 rz1 sliced rootdg 512 2 173 2 26 4109952 /dev/rz1g YES
Please notice the PUBPATH - re0 has partition g, re1-re5 have patrition h.
Voldisksetup is successful for re0, but re1 - re5 only results in a state "online aliased" due to the wrong PUBPATH (I guess).
# voldisk list re1
Device: re1
devicetag: re1
type: sliced
hostid: dsu20t
disk: name= id=849860405.1175.dsu20t
group: name=t20dg id=849860383.1170.dsu20t
flags: online ready private aliased
pubpaths: block=/dev/re1g char=/dev/rre1g
privpaths: block=/dev/re1h char=/dev/rre1h
version: 1.1
iosize: 512
public: slice=7 offset=0 len=25134576
private: slice=6 offset=16 len=512
update: time=912768299 seqno=0.240
headers: 0 248
configs: count=2 len=173
logs: count=2 len=26
Any ideas how to convince voldisksetup to set the disks "online" ?
Thanks in advance, will summarize
Peter
Peter.Braack_at_degussa.de
Received on Mon Dec 07 1998 - 10:39:16 NZDT