Printable View
I have Volume Manager v4.1 running on Solaris 10.
I am getting the following error message when trying to create new volumes
$vxassist -g dg01 make volume21 10G layout=stripe disk1 disk2
VxVM vxassist ERROR V-5-1-10127 creating subdisk disk1-21:
Subdisk disk1-21 would overlap subdisk disk1-01
This command is precisely how I created volumes 1-20. There is ample free
space remaining in the disk group.
post "vxdg -g dg01 free"
as well as
vxprint -thg dg01
and lastly
vxassist -g maxsize layout=stripe disk1 disk2
What I want to see is the location of the sub-disk disk1-01
It depends what each disk (disk1 and 2 - but specifically disk1) has got
left space-wise.
Terry Webber wrote:[color=blue]
> I have Volume Manager v4.1 running on Solaris 10.
>
> I am getting the following error message when trying to create new volumes
>
> $vxassist -g dg01 make volume21 10G layout=stripe disk1 disk2
>
> VxVM vxassist ERROR V-5-1-10127 creating subdisk disk1-21:
> Subdisk disk1-21 would overlap subdisk disk1-01
>
> This command is precisely how I created volumes 1-20. There is ample free
> space remaining in the disk group.
>
>[/color]
I noticed this last nite; somehow the free space is being reported incorrectly
for disk1. I suppose that is resulting in offset 0 being used for new volumes,
causing the overlay error.
hmmmm, this began after a StorageTek visit to reconfig (yet again) our SAN
to fix some problems.
#vxdg -g dg01 free
GROUP DISK DEVICE TAG OFFSET LENGTH FLAGS
dg01 disk1 c2t1d0s2 c2t1d0 0 498046448 n
dg01 disk2 c2t1d1s2 c2t1d1 155957248 342089200 n
#vxprint -thg dg01
DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME NVOLUME KSTATE STATE
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX
UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID
MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE
MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM
MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE
MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
dg dg01 default default 31000 1120942809.76.sun0g
dm disk1 c2t1d0s2 auto 4096 498046448 NOHOTUSE
dm disk2 c2t1d1s2 auto 4096 498046448 NOHOTUSE
v oralocs_arc01 - ENABLED ACTIVE 27262976 SELECT oralocs_arc01-
01 fsgen
pl oralocs_arc01-01 oralocs_arc01 ENABLED ACTIVE 27262976 STRIPE 2/128
RW
sd disk1-01 oralocs_arc01-01 disk1 0 13631488 0/0 c2t1d0
ENA
sd disk2-01 oralocs_arc01-01 disk2 0 13631488 1/0 c2t1d1
ENA
#vxassist -g dg01 maxsize layout=stripe disk1 disk2
Maximum volume size: 684177408 (334071Mb)
Me <me@hotmail.com> wrote:[color=blue]
>post "vxdg -g dg01 free"
>
>as well as
> vxprint -thg dg01
>
>
>and lastly
> vxassist -g maxsize layout=stripe disk1 disk2
>
>
>
>
>What I want to see is the location of the sub-disk disk1-01
>
>It depends what each disk (disk1 and 2 - but specifically disk1) has got[/color]
[color=blue]
>left space-wise.
>
>Terry Webber wrote:[color=green]
>> I have Volume Manager v4.1 running on Solaris 10.
>>
>> I am getting the following error message when trying to create new volumes
>>
>> $vxassist -g dg01 make volume21 10G layout=stripe disk1 disk2
>>
>> VxVM vxassist ERROR V-5-1-10127 creating subdisk disk1-21:
>> Subdisk disk1-21 would overlap subdisk disk1-01
>>
>> This command is precisely how I created volumes 1-20. There is ample free
>> space remaining in the disk group.
>>
>>[/color][/color]
The problem is fixed. The configuration database became corrupt somehow. The
following command rebuilt it without disruption.
'vxconfigd -k -x cleartempdir'
Thanks for your help.
t