1829753 Members
2779 Online
109992 Solutions
New Discussion

vgextend fails

 
SOLVED
Go to solution
BOB BRASON_1
Occasional Contributor

vgextend fails

Hi Admins,
I have a problem in extending a volume from an 12H Autoraid box.I believe I have followed the right procedure,anyhow this is what I did
created LUN eg.arraycfg -L -a
then ran ioscan to pickup the disk,then pvcreate eg,pvcreate /dev/rdsk/c4t4d1,then vgextend eg,vgextend /dev/vg02 /dev/dsk/c4t4d1 that's where it fails with "Can't open Physical Volume /dev/dsk/c4t4d1".
see attached output.
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 6 8/0/19/0.1.0 sdisk CLAIMED DEVICE COMPAQ BD009734A3
/dev/dsk/c1t1d0 /dev/rdsk/c1t1d0
disk 1 8/0/19/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST39140WS
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 4 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-6201TA
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 3 10/0/2/0.4.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c4t4d0 /dev/rdsk/c4t4d0
disk 7 10/0/2/0.4.1 sdisk CLAIMED DEVICE HP C5447A
#vgdisplay -v /dev/vg02

Volume Groups

VG Name /dev/vg02
VG Write Access read/write
VG Status Available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 15360
VGDA 2
PE size (mb) 16
Total PE 8143
Alloc PE 8142
Free PE 1
Total PVG 0

Logical Volumes

LV Name /dev/vg02/raid01
LV status available/syncd
LV size (mb) 130272
Current LE 8142
Allocate LE 8142
Used PV 1

Physical Volumes

PV Name /dev/dsk/c4t4d0
PV Status Available
Total PE 8143
Free PE 1

#lvdisplay -v /dev/vg02/raid01

Logical Volumes

LV Name /dev/vg02/raid01
VG Name /dev/vg02
LV Permission read/write
LV Status available/syncd
Mirror Copies 0
Consistancy Recovery MWC
Schedule Parallel
LV size (mb) 130272
Current LE 8142
Allocated PE 8142
Stripes 0
Stripe size (kb) 0
Bad block on
Allocation strict
IO timeout (sec) default

Distribution of Logical Volume

PV Name LE on PV PE on PV
/dev/dsk/c4t4d0 8142 8142

Logical Extents

LE PV1 PE1 Status1
0000 /dev/dsk/c4t4d0 0000 Current
through to
8141 /dev/dsk/c4t4d0 8141 Current

#arraydsp -a

Vendor ID HP
Product ID C5447A
Array Ser No 0000001373DB
Array State Ready
Server name thame
Array type 3
Mfg Prod Code IJMTU00004

Disk Space Usage

Total Physical 277863mb
Allocated to UNs 130309mb
Used as hot spare 34732mb
Used by non inc disks 0mb
Used for redundancy 49739mb
Unallocated(Av for LUNs)63083mb



#swlist -l product | grep JFS

PHKL_16750 B.10.00.00.AA SIG_IGN/SIGCLD,LVM,JFS,PC1/SCSI Cumulative Patch
PHKL_17206 B.10.00.00.AA Fix large buffer write gets VX_ERETRY on JFS
PHKL_17518 B.10.00.00.AA JFS Corruption; stk overflow, dirty inval panics
PHKL_17520 B.10.00.00.AA JFS fsadm ENOSPC,Performance improvement patch
PHKL_17526 B.10.00.00.AA JFS Sync/freeze ddirty inval panic patch
PHKL_20355 B.10.00.00.AA Adv JFS; fix direct read to return correct error

#df

/tmp_mnt/genesis (reading2:/genesis) 60623560 Blocks
/home (/dev/vg00/lvol4) 381272 Blocks
/opt (/dev/vg00/lvol5) 405980 Blocks
/raid01 (/dev/vg02/raid01) 15597268 Blocks
/star (/dev/vg04/star) 6904756 Blocks
/tmp (/dev/vg00/lvol6) 123106 Blocks
/usr (/dev/vg00/lvol7) 725628 Blocks
/dev/rdsk/c4t4d1

10 points for resolving!
many thanks
mo
7 REPLIES 7
Rita C Workman
Honored Contributor

Re: vgextend fails

Are you certain the pvcreate actually took...

Try going back and running :
pvcreate -f /dev/dsk/c4t4d1

Then see if it will allow you to vgextend at that point.

Just a thought,
Rita
Pete Randall
Outstanding Contributor

Re: vgextend fails

You say you're trying to run vgextend on c4t4d1 ("vgextend /dev/vg02 /dev/dsk/c4t4d1"), yet your df output appears to show c4t4d1 mounted. Are you sure you created the LUN correctly and didn't duplicate an existing one? Have you got it mounted somehow? What does the mount command say about c4t4d1?


Pete

Pete
Kent Ostby
Honored Contributor

Re: vgextend fails

A couple of things.

It doesn't appear to show c4t4d1 in the ioscan output.

Also, it does show c4t4d1 in "df" output.

Check to see if "diskinfo /dev/rdsk/c4t4d1" returns proper data or if it also shows "cannot open device".

If it shows cannot open device then the problem is at the LUN creation level.

Best regards,

Kent M. Ostby
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
Dietmar Konermann
Honored Contributor
Solution

Re: vgextend fails

Looking at your ioscan I see no device files for the LUN. Then I find the rdsk lost at the end of your post. Are both device files there (rdsk+dsk)?? Run "insf -eH 10/0/2/0.4.1" ant try again.

Best regards...
Dietmar.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
BOB BRASON_1
Occasional Contributor

Re: vgextend fails

Hi Dietmar,
That has worked but now I have another problem
when I extend the logical volume eg,lxextend -L 63083 /dev/vg02/raid01 it fails with "Logical Extent Number" is not bigger than current setting.
What does this mean
many thanks
Muhammad Jahangir Mirza
Occasional Contributor

Re: vgextend fails

Hi, Mirza
i think you use this command
lvextend -L (size) -n (logical vol name) /dev/dsk/VG

thnks
Muhammad Jahangir Mirza
Occasional Contributor

Re: vgextend fails

Hi, Mirza
i think you use this command
# lvextend [-l|-L] /dev/vgYY/lvolZ
# extendfs /dev/vgYY/lvolZ
# mount /dev/vgYY/lvolZ /


thnks