From: Andres Rojas (arojasm@adexus.cl)
Date: Fri Apr 23 2004 - 20:38:27 EDT
Dear Managers,
I will try to explain the situation experienced the best as my short
english will allow me.
This is a Volume Manager 3.1.1 under Solaris 2.6 configuration. If this is
out of scope please excuse me.
During the creation of a new volume under group disk "arraybds" one of the
blank disks (blanked by removing it's partitions with "format") was
identified to contain a valid VTOC and offered to be encapsulated instead
of initialized (pardon?). The encapsulation offered the arraybd18 disk
name. Since I wanted to effectively initialize I requested for
initialization and the arraybd19 disk name was offered.
After a test boot all the volumes in the group disk dissapeared with the
exception of disk arraybd18. The remaining diskgroup survived with no
problem. The execution of vxdisk list over one of the missing disks shown
the following output:
<pre>
Device: c4t18d0s2
devicetag: c4t18d0
type: sliced
hostid:
disk: name= id=1082297848.47740.buseo
group: name=arraybds id=1082216191.47505.buseo
flags: online ready private autoconfig
pubpaths: block=/dev/vx/dmp/c4t18d0s4 char=/dev/vx/rdmp/c4t18d0s4
privpaths: block=/dev/vx/dmp/c4t18d0s3 char=/dev/vx/rdmp/c4t18d0s3
version: 2.1
iosize: min=512 (bytes) max=2048 (blocks)
public: slice=4 offset=0 len=17678493
private: slice=3 offset=1 len=3590
update: time=1082302563 seqno=0.9
headers: 0 248
configs: count=1 len=2630
logs: count=1 len=398
Defined regions:
config priv 000017-000247[000231]: copy=01 offset=000000 disabled
config priv 000249-002647[002399]: copy=01 offset=000231 disabled
log priv 002648-003045[000398]: copy=01 offset=000000 disabled
Multipathing information:
numpaths: 1
c4t18d0s2 state=enabled
</pre>
The disk belongs to the disk group but due to the poor knowledge of the
product there was no quick solution rather than create the disk group from
scratch and recover from backups.
I was able to partially reproduce this behavior under Solaris 8 and VxVM
3.5.
Note: Do not attempt to reproduce this problem in a productive disk group.
Create a new one and make your tests since it seems to affect the disk
group you are configuring only.
Does anyone know what causes this problem?
Thanks as usual,
- Andres.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:28:31 EDT