Creating new volume group through SAM taking ages.

[martin clarke_1]

After getting some advice in an earlier thread I am trying to allocate a 146gig physical volume as a new volume group.

Using SAM I selected the unused physical volume and chose the option to create a new volume group VG02 with a new LV of LV13
(already up to LV12).The config was left as defaults to create a LV to utilise 140012 meg from the new disk and to mount it as /data2.
SAM has been displaying the "creating volume group" message for over an hour. The rotating line within brakets on the SAM screen continues to rotate indicating that something is happening. The screen is locked. I have been watching the disk activity lights and no activity seems to be taking place on the new drive. How long should this take.

[Steven E. Protter · Accepted solution]

open up a net terminal session.

run the top command, see if lvcreate is on thelist and doing anything.

If yes, let it go.

If not, something went wrong and you might want to stop the process.

I personally would not use sam for this purpose. I'm not saying sam can't do it, but probably there is a problem that sam didn't pick up and thats hanging things up.

strings /etc/lvmtab

make sure there are no references to the disks you have added to this volume group.

A disk can't be in two volume groups.

I need more data to further assist.

SEP

[Todd McDaniel_1]

I never use SAM for LVM work. My personal preference is do this LVM work from the command line.

However, 146GB is a lot of data... But I make 70GB filessytems from the command line and it takes about 30 seconds.

Id say your session is hung. Id rlogin over to it from another box and kill SAM and try kill the lvm procs.


IF you can get it to quit. I would look into doing it from the command line. I dont like the overhead of SAM for intricate work such as LVM.

[Mark Greene_1]

It may be hung on trying to create the new volume group. Login again and see if you can do a vgdisplay on VG02 or not.

If you are running ServiceGuard, you may have other conflicts/problems to deal with, and I'd advise calling HP support for that.

I'll also echo the others and point you to the man pages for vgcreate and lvcreate and recommend doing all this from the commandline.

mark

[martin clarke_1]

Well thanks again everyone.

Being a bit of a novice on HPUX system admin I was hoping SAM would do it all for me.
To get everything up and running again I killed of two SAM processes and a vgcreate process which seemed to have hung.
The console was then stuck in SAM screen mode and would not respond. Ended up rebooting the system. Everything is back to where I started so I will have to read up on doing it manually.

[Pete Randall]

Martin,

The steps are pvcreate, vgcreate, lvcreate and newfs. A perusal of the man pages should get you going.


Pete

[Todd McDaniel_1]

Here is an example of a striped filesystem 2 Lvols... with 70G filesystems 8-9GB disks....

# cat vgoradt30.sh
#pvcreate
#mkdir /dev/vgoradt30
#mknod /dev/vgoradt30/group c 64 0x3d0000

vgcreate -p 64 /dev/vgoradt30

#vgextend /dev/vgoradt30


#lvcreate -n oradt_fs101 /dev/vgoradt30
#lvcreate -n oradt_fs102 /dev/vgoradt30


#lvcreate -i 8 -I 128 -n oradt_fs101 -r n /dev/vgoradt30
#lvcreate -i 8 -I 128 -n oradt_fs102 -r n /dev/vgoradt30


#lvextend -l 17256 /dev/vgoradt30/oradt_fs101

#lvextend -l 17256 /dev/vgoradt30/oradt_fs102

#newfs -F vxfs /dev/vgoradt30/roradt_fs101
#newfs -F vxfs /dev/vgoradt30/roradt_fs102
mount /dev/vgoradt30/oradt_fs101 /oradata/fs101
mount /dev/vgoradt30/oradt_fs102 /oradata/fs102

[martin clarke_1]

I have just finished moving offices so there has been a bit of a delay since my last response.

Anyway, /dev/lvmtab has already got an entry for vg02 but sam doesnt seem to detect an volume groups apart from vg00. How do I remove the vg02 entry.