[newbie] Adding and configuring new disk

Hi ! I've little experience on HP-UX, and never added a disk. I own a used C8000, from the new wave of low cost ones ... It had a 36GB disk, configured as follow Volume groups ============= Name Type MBytes avail. Phys Vol. Log. Vol. vg00 LVM 19848 of 34720 1 8 Logical Volumes =============== lvol1 vg00 LVM HFS 304 0 /stand lvol2 vg00 LVM Swap/Dump 4096 0 lvol3 vg00 LVM VxFS 200 0 / lvol4 vg00 LVM VxFS 200 0 /tmp lvol5 vg00 LVM VxFS 24 0 /home lvol6 vg00 LVM VxFS 3168 0 /opt lvol7 vg00 LVM VxFS 2280 0 /usr lvol8 vg00 LVM VxFS 4600 0 /var File Systems ============ / VxFS /dev/vg00/lvol3 /home VxFS /dev/vg00/lvol5 /opt VxFS /dev/vg00/lvol6 /stand HFS /dev/vg00/lvol1 /tmp VxFS /dev/vg00/lvol4 /usr VxFS /dev/vg00/lvol7 /var VxFS /dev/vg00/lvol8 Now I added a 73GB U320 10k disk. How would you configure it ? Can I add it to /home and /usr ? Help will be greatly appreciated :)

supervinx <nessuno@libero.it> writes: > Hi ! > I've little experience on HP-UX, and never added a disk. > I own a used C8000, from the new wave of low cost ones ... > It had a 36GB disk, configured as follow > > Volume groups > ============= > Name Type MBytes avail. Phys Vol. Log. Vol. > vg00 LVM 19848 of 34720 1 8 > > Logical Volumes > =============== > lvol1 vg00 LVM HFS 304 0 /stand > lvol2 vg00 LVM Swap/Dump 4096 0 > lvol3 vg00 LVM VxFS 200 0 / > lvol4 vg00 LVM VxFS 200 0 /tmp > lvol5 vg00 LVM VxFS 24 0 /home > lvol6 vg00 LVM VxFS 3168 0 /opt > lvol7 vg00 LVM VxFS 2280 0 /usr > lvol8 vg00 LVM VxFS 4600 0 /var > > File Systems > ============ > / VxFS /dev/vg00/lvol3 > /home VxFS /dev/vg00/lvol5 > /opt VxFS /dev/vg00/lvol6 > /stand HFS /dev/vg00/lvol1 > /tmp VxFS /dev/vg00/lvol4 > /usr VxFS /dev/vg00/lvol7 > /var VxFS /dev/vg00/lvol8 > > > Now I added a 73GB U320 10k disk. > > How would you configure it ? > Can I add it to /home and /usr ? > Help will be greatly appreciated :) Use the pvcreate command to create a physical volume of the disk. Then you add the physical volume to volume group vg00 using the command vgextend. After that you extend the logical volumes you want to be extended using the command lvextend. That should do it ... HTH. Frank

Frank GOENNINGER <dg1sbg@googlemail.com> wrote: >supervinx <nessuno@libero.it> writes: > >> Hi ! >> I've little experience on HP-UX, and never added a disk. >> I own a used C8000, from the new wave of low cost ones ... >> It had a 36GB disk, configured as follow >> >> Volume groups >> ============= >> Name Type MBytes avail. Phys Vol. Log. Vol. >> vg00 LVM 19848 of 34720 1 8 >> >> Logical Volumes >> =============== >> lvol1 vg00 LVM HFS 304 0 /stand >> lvol2 vg00 LVM Swap/Dump 4096 0 >> lvol3 vg00 LVM VxFS 200 0 / >> lvol4 vg00 LVM VxFS 200 0 /tmp >> lvol5 vg00 LVM VxFS 24 0 /home >> lvol6 vg00 LVM VxFS 3168 0 /opt >> lvol7 vg00 LVM VxFS 2280 0 /usr >> lvol8 vg00 LVM VxFS 4600 0 /var >> >> File Systems >> ============ >> / VxFS /dev/vg00/lvol3 >> /home VxFS /dev/vg00/lvol5 >> /opt VxFS /dev/vg00/lvol6 >> /stand HFS /dev/vg00/lvol1 >> /tmp VxFS /dev/vg00/lvol4 >> /usr VxFS /dev/vg00/lvol7 >> /var VxFS /dev/vg00/lvol8 >> >> >> Now I added a 73GB U320 10k disk. >> >> How would you configure it ? >> Can I add it to /home and /usr ? >> Help will be greatly appreciated :) > >Use the pvcreate command to create a physical volume of the disk. Then >you add the physical volume to volume group vg00 using the command >vgextend. > >After that you extend the logical volumes you want to be extended using >the command lvextend. > >That should do it ... > >HTH. > >Frank Finally, you will need to extend the file system to use the extra space on the logical volume, fsadm fie vxfs file systems. Or use SAM to add the disk to VG00 and then increase the filesystems Ted. ============================================================== | Ted Linnell <edlinnell@acslink.net.au> | | | | Nunawading, Victoria , Australia | ==============================================================

Il Sun, 09 Jan 2011 20:00:02 +0100, Frank GOENNINGER ha scritto: > supervinx <nessuno@libero.it> writes: > >> Hi ! >> I've little experience on HP-UX, and never added a disk. I own a used >> C8000, from the new wave of low cost ones ... It had a 36GB disk, >> configured as follow >> >> Volume groups >> ============= >> Name Type MBytes avail. Phys Vol. Log. Vol. vg00 LVM >> 19848 of 34720 1 8 >> >> Logical Volumes >> =============== >> lvol1 vg00 LVM HFS 304 0 /stand >> lvol2 vg00 LVM Swap/Dump 4096 0 lvol3 >> vg00 LVM VxFS 200 0 / lvol4 >> vg00 LVM VxFS 200 0 /tmp lvol5 >> vg00 LVM VxFS 24 0 /home lvol6 >> vg00 LVM VxFS 3168 0 /opt lvol7 >> vg00 LVM VxFS 2280 0 /usr lvol8 >> vg00 LVM VxFS 4600 0 /var >> >> File Systems >> ============ >> / VxFS /dev/vg00/lvol3 >> /home VxFS /dev/vg00/lvol5 >> /opt VxFS /dev/vg00/lvol6 >> /stand HFS /dev/vg00/lvol1 >> /tmp VxFS /dev/vg00/lvol4 >> /usr VxFS /dev/vg00/lvol7 >> /var VxFS /dev/vg00/lvol8 >> >> >> Now I added a 73GB U320 10k disk. >> >> How would you configure it ? >> Can I add it to /home and /usr ? >> Help will be greatly appreciated :) > > Use the pvcreate command to create a physical volume of the disk. Then > you add the physical volume to volume group vg00 using the command > vgextend. > > After that you extend the logical volumes you want to be extended using > the command lvextend. > > That should do it ... > > HTH. > > Frank Too good, too easy :( VGs and LVMs begin to be more clear, but I encountered some problems. Original situation: single disk, 36GB, one VG, 8 LVMs ================== lvol1 /stand 304 lvol2 swap 4096 lvol3 / 200 lvol4 /tmp 200 lvol5 /home 24 lvol6 /opt 3168 lvol7 /usr 2280 lvol8 /var 4600 First question: summing all lvols except lvol5 (/home) gives 14848 MB. Where are the missing MBs ? /home is so small, 24 MB and gives me odd behaviour (I'll explain later) Added a 73GB disk. Tried to use SAM: extended the VG but couldn't extend LVMs and FS (I left untouched lvol1-lvol3, contiguous allocation, and lvol2, swap) because everything was mounted. Did init s, but couldn't umount. So rebooted,, interacted with IPL, HPUX -is. For lvols 4,6,7,8 had no troubles. (/tmp) # lvextend -L 1024 /dev/vg00/lvol4 # extendfs /dev/vg00/lvol4 (/opt) # lvextend -L 10240 /dev/vg00/lvol6 # extendfs /dev/vg00/lvol6 (/usr) # lvextend -L 10240 /dev/vg00/lvol7 # extendfs /dev/vg00/lvol7 (/var) # lvextend -L 10240 /dev/vg00/lvol8 # extendfs /dev/vg00/lvol8 Now, used space in the VG00 should be 10240x3+1024+4096+200+304=32654, out of 36+73=109GB When tried to extend lvol5 (/home) # lvextend -L size /dev/vg00/lvol5 size couldn't be more than 33600. ???? A lot less than SAM calculated before. extended the FS in /home, rebooted. Fired up SAM, all FS were correctly extended. /home is still at 24 MB ! but VG00 shows almost no free space. only 88 MB. There's something I don't know about HP-UX disk policy.

# vgdisplay -v vg00 --- Volume groups --- VG Name /dev/vg00 VG Write Access read/write VG Status available Max LV 255 Cur LV 8 Open LV 8 Max PV 16 Cur PV 2 Act PV 2 Max PE per PV 4350 VGDA 4 PE Size (Mbytes) 8 Total PE 8690 Alloc PE 8679 Free PE 11 Total PVG 0 Total Spare PVs 0 Total Spare PVs in use 0 --- Logical volumes --- LV Name /dev/vg00/lvol1 LV Status available/syncd LV Size (Mbytes) 304 Current LE 38 Allocated PE 38 Used PV 1 LV Name /dev/vg00/lvol2 LV Status available/syncd LV Size (Mbytes) 4096 Current LE 512 Allocated PE 512 Used PV 1 LV Name /dev/vg00/lvol3 LV Status available/syncd LV Size (Mbytes) 200 Current LE 25 Allocated PE 25 Used PV 1 LV Name /dev/vg00/lvol4 LV Status available/syncd LV Size (Mbytes) 512 Current LE 64 Allocated PE 64 Used PV 1 LV Name /dev/vg00/lvol5 LV Status available/syncd LV Size (Mbytes) 33600 <======= ???? Current LE 4200 Allocated PE 4200 Used PV 2 LV Name /dev/vg00/lvol6 LV Status available/syncd LV Size (Mbytes) 10240 Current LE 1280 Allocated PE 1280 Used PV 2 LV Name /dev/vg00/lvol7 LV Status available/syncd LV Size (Mbytes) 10240 Current LE 1280 Allocated PE 1280 Used PV 1 LV Name /dev/vg00/lvol8 LV Status available/syncd LV Size (Mbytes) 10240 Current LE 1280 Allocated PE 1280 Used PV 1 --- Physical volumes --- PV Name /dev/dsk/c0t6d0 (36GB) PV Status available Total PE 4340 Free PE 0 Autoswitch On PV Name /dev/dsk/c0t0d0 (73GB) PV Status available Total PE 4350 <======== ?????? Free PE 11 Autoswitch On ============================================ I add these infos: # mount / on /dev/vg00/lvol3 log on Mon Jan 10 23:22:07 2011 /stand on /dev/vg00/lvol1 defaults on Mon Jan 10 23:22:08 2011 /var on /dev/vg00/lvol8 delaylog,nodatainlog on Mon Jan 10 23:22:11 2011 /usr on /dev/vg00/lvol7 delaylog,nodatainlog on Mon Jan 10 23:22:11 2011 /tmp on /dev/vg00/lvol4 delaylog,nodatainlog on Mon Jan 10 23:22:11 2011 /opt on /dev/vg00/lvol6 delaylog,nodatainlog on Mon Jan 10 23:22:11 2011 /home on /dev/vg00/lvol5 delaylog,nodatainlog on Mon Jan 10 23:22:12 2011 # lvdisplay /dev/vg00/lvol5 --- Logical volumes --- LV Name /dev/vg00/lvol5 VG Name /dev/vg00 LV Permission read/write LV Status available/syncd Mirror copies 0 Consistency Recovery MWC Schedule parallel LV Size (Mbytes) 33600 Current LE 4200 Allocated PE 4200 Stripes 0 Stripe Size (Kbytes) 0 Bad block on Allocation strict IO Timeout (Seconds) default # df /home (/dev/vg00/lvol5 ): 44272 blocks 668 i-nodes /opt (/dev/vg00/lvol6 ): 15519424 blocks 244394 i-nodes /tmp (/dev/vg00/lvol4 ): 1035552 blocks 16294 i-nodes /usr (/dev/vg00/lvol7 ): 17096480 blocks 269225 i-nodes /var (/dev/vg00/lvol8 ): 20170512 blocks 317609 i-nodes /stand (/dev/vg00/lvol1 ): 388960 blocks 32646 i-nodes / (/dev/vg00/lvol3 ): 175200 blocks 2753 i-nodes I did the same operations on lvol4 to lvol8. All FS have been extended, /home no. But just after the first, clean installation, /home was of 24 MB, and lot of GBs were missing. Even if I have no experience, I noticed some things: Max PE per PV 4350 PE Size (Mbytes) 8 for every disk, so the 73GB is treated as a 36GB. May be this is the reason why I got an "extent" error with extendfs. But, even with this error, why /home can't be extended ? May I join differently sized disk in a VG ? Thanks for your patience !

addendum in multiuser mode (normal startup) did again these operations: 1) umount /home 2) extendfs /dev/vg00/lvol5 3) mount /home. Now # df /home /home (/dev/vg00/lvol5): 68268624 blocks 1075068 i-nodes May be the solution is near ... it should be related to extent size (8MB) and max PE per PV

> > May I join differently sized disk in a VG ? > It can be joined, but VG parameter will limit number of PEs that can be used from that disk. By default limit is deifined with the size of first disk.

Il Tue, 11 Jan 2011 08:25:01 +0100, Mario ha scritto: >> May I join differently sized disk in a VG ? >> >> > It can be joined, but VG parameter will limit number of PEs that can be > used from that disk. By default limit is deifined with the size of first > disk. So, since I did a fresh installation and no other data are present, I could reduce the VG at original values, unconfiguring the 73GB disk and add one or two 36GB disk, sized as the first disk. If I create a new VG, say VG01 associated to the 73GB disk PV, I must create new LVMs, right ? New LVMs, new mount points... I think the best solution is equally sized disks. Or, reinstall it again starting from 73GB disks :P

Il Tue, 11 Jan 2011 07:26:50 +0000, supervinx ha scritto: > Il Tue, 11 Jan 2011 08:25:01 +0100, Mario ha scritto: > > >>> May I join differently sized disk in a VG ? >>> >>> >> It can be joined, but VG parameter will limit number of PEs that can be >> used from that disk. By default limit is deifined with the size of >> first disk. > > So, since I did a fresh installation and no other data are present, I > could reduce the VG at original values, unconfiguring the 73GB disk and > add one or two 36GB disk, sized as the first disk. > > If I create a new VG, say VG01 associated to the 73GB disk PV, I must > create new LVMs, right ? > > New LVMs, new mount points... > > I think the best solution is equally sized disks. Or, reinstall it again > starting from 73GB disks :P Reinstalling :( Discovered, at my expense, that FS can't be reduced so easily. Reduced the LVMs and got system unusable excpet single user mode. Useful experience and harmless. The C800 wasn't operative, yet. The only additional sw was Ximian Gnome. Now I must plan carefully the new installation (and new disks adding). The only drawback is the idiosyncrasy of my C800 towards IDE CDROM/DVDROM. Must connect a SCSI one "on the fly", bah ... :P A last thing: if I put a 73GB disk and then add to the VG a 36GB disk, the free extents will be related to the 73GB disk ? So in the second PV I will have more 8MB extents than physical free space, right ?

supervinx <nessuno@libero.it> wrote: >Il Tue, 11 Jan 2011 07:26:50 +0000, supervinx ha scritto: > >> Il Tue, 11 Jan 2011 08:25:01 +0100, Mario ha scritto: >> >> >>>> May I join differently sized disk in a VG ? >>>> >>>> >>> It can be joined, but VG parameter will limit number of PEs that can be >>> used from that disk. By default limit is deifined with the size of >>> first disk. >> >> So, since I did a fresh installation and no other data are present, I >> could reduce the VG at original values, unconfiguring the 73GB disk and >> add one or two 36GB disk, sized as the first disk. >> >> If I create a new VG, say VG01 associated to the 73GB disk PV, I must >> create new LVMs, right ? >> >> New LVMs, new mount points... >> >> I think the best solution is equally sized disks. Or, reinstall it again >> starting from 73GB disks :P > >Reinstalling :( >Discovered, at my expense, that FS can't be reduced so easily. >Reduced the LVMs and got system unusable excpet single user mode. >Useful experience and harmless. The C800 wasn't operative, yet. >The only additional sw was Ximian Gnome. >Now I must plan carefully the new installation (and new disks adding). >The only drawback is the idiosyncrasy of my C800 towards IDE CDROM/DVDROM. >Must connect a SCSI one "on the fly", bah ... :P > >A last thing: if I put a 73GB disk and then add to the VG a 36GB disk, >the free extents will be related to the 73GB disk ? So in the second PV I >will have more 8MB extents than physical free space, right ? No. The limit is the number of PEs per disk, and the PE size is set on the first disk in the VG. All subsequent disk added must use the same PE size. If you start with a small disk and use the default PE size it will set the smallest PE size that will allow the entire disk to be used. If you the add a larger disk, you only get the space allowed by the maximum PE of this smaller size. If you start with a larger disk, PE size is set larger, to allow use of the entire disk. Adding a smaller disk uses this larger PE size so you get access to the entire disk, just have less PEs on it. Ted. ============================================================== | Ted Linnell <edlinnell@acslink.net.au> | | | | Nunawading, Victoria , Australia | ==============================================================

Il Wed, 12 Jan 2011 09:40:54 +1100, Ted Linnell ha scritto: > supervinx <nessuno@libero.it> wrote: > >>Il Tue, 11 Jan 2011 07:26:50 +0000, supervinx ha scritto: >> >>> Il Tue, 11 Jan 2011 08:25:01 +0100, Mario ha scritto: >>> >>> >>>>> May I join differently sized disk in a VG ? >>>>> >>>>> >>>> It can be joined, but VG parameter will limit number of PEs that can >>>> be used from that disk. By default limit is deifined with the size of >>>> first disk. >>> >>> So, since I did a fresh installation and no other data are present, I >>> could reduce the VG at original values, unconfiguring the 73GB disk >>> and add one or two 36GB disk, sized as the first disk. >>> >>> If I create a new VG, say VG01 associated to the 73GB disk PV, I must >>> create new LVMs, right ? >>> >>> New LVMs, new mount points... >>> >>> I think the best solution is equally sized disks. Or, reinstall it >>> again starting from 73GB disks :P >> >>Reinstalling :( >>Discovered, at my expense, that FS can't be reduced so easily. Reduced >>the LVMs and got system unusable excpet single user mode. Useful >>experience and harmless. The C800 wasn't operative, yet. The only >>additional sw was Ximian Gnome. Now I must plan carefully the new >>installation (and new disks adding). The only drawback is the >>idiosyncrasy of my C800 towards IDE CDROM/DVDROM. Must connect a SCSI >>one "on the fly", bah ... :P >> >>A last thing: if I put a 73GB disk and then add to the VG a 36GB disk, >>the free extents will be related to the 73GB disk ? So in the second PV >>I will have more 8MB extents than physical free space, right ? > > No. The limit is the number of PEs per disk, and the PE size is set on > the first disk in the VG. All subsequent disk added must use the same PE > size. > > If you start with a small disk and use the default PE size it will set > the smallest PE size that will allow the entire disk to be used. If you > the add a larger disk, you only get the space allowed by the maximum PE > of this smaller size. > > If you start with a larger disk, PE size is set larger, to allow use of > the entire disk. > Adding a smaller disk uses this larger PE size so you get access to the > entire disk, just have less PEs on it. > > Ted. > ============================================================== | Ted > Linnell <edlinnell@acslink.net.au> | | > | > | Nunawading, Victoria , Australia | > ============================================================== You've been *extremely* clear and concise, thanks ! I'll put the largest disk first, so if I'm in need of extending the VG, can add a smaller disk. Thanks again !

Similiar Articles:

[newbie] Adding and configuring new disk - comp.sys.hp.hpux ...
Hi ! I've little experience on HP-UX, and never added a disk. I own a used C8000, from the new wave of low cost ones ... It had a 36GB disk, config...

SAN disk on hp-ux - comp.sys.hp.hpux
I've little experience on HP-UX, and never added a disk. I own a used C8000, from the new ... SAN disk on hp-ux - comp.sys.hp.hpux [newbie] Adding and configuring new disk ...

Recovery disk needed for Gateway M465 - comp.sys.laptops ...
Also, if the installation disk for XP loaded all the device drivers that IT thought were correct and you find that some are wrong there is only one way that is long and ...

Solaris 10 not adding new SAN disks with devfsadm? - comp.unix ...
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... Solaris 10 not adding new SAN disks with devfsadm? - comp.unix ... [newbie] Adding and configuring new disk ...

lvextend: "LogicalExtentsNumber" is not bigger than current ...
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ..... you want to be extended using the command lvextend. ... Size (Mbytes) 304 Current ... > > If you start ...

Adding "New Page" to Document Menu in Acrobat - comp.text.pdf ...
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... [newbie] Adding and configuring new disk - comp.sys.hp.hpux ... Use the pvcreate command to create a ...

Check disk errors in hp-ux - comp.sys.hp.hpux
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... I've little experience on HP-UX, and never added a disk. I own a used C8000, from the new wave ...

Converting LVM disks to vxfs - comp.sys.hp.hpux
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... I've little experience on HP-UX, and never added a disk. I own a used C8000 ... LVM Swap/Dump 4096 0 lvol3 ...

metadb problem - comp.unix.solaris
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... metadb problem - comp.unix.solaris Perfect timing for getting a new disk :-) # metadb -i ...

Disk cylinder, blocks information from OBP - comp.sys.sun.admin ...
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ..... home (/dev/vg00/lvol5): 68268624 blocks ... new ... description: Migrating "clustered" data from one disk ...

Sending SCSI passthrough commands to SATA drives - comp.periphs ...
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ..... be greatly appreciated :) Use the pvcreate command to ... Must connect a SCSI one "on the fly", bah ...

configure a hpux box as a dns client - comp.sys.hp.hpux
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... configure a hpux box as a dns client - comp.sys.hp.hpux [newbie] Adding and configuring new disk - comp.sys ...

Raw devices in non-global zone - comp.unix.solaris
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... Raw devices in non-global zone - comp.unix.solaris [newbie] Adding and configuring new disk - comp.sys.hp ...

Getting slice/volume size from kernel mode - comp.unix.solaris ...
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... It had a 36GB disk, configured as follow Volume groups ... When tried to extend lvol5 (/home) # lvextend -L ...

Adding a second CPU to a DS20E - comp.os.vms
[newbie] Adding and configuring new disk - comp.sys.hp.hpux ... Adding a second CPU to a DS20E - comp.os.vms [newbie] Adding and configuring new disk - comp.sys.hp.hpux ...

Adding/removing SATA drive - LinuxQuestions.org
... Linux Forums > Linux - Newbie: Adding/removing SATA drive ... up to Fedora with this drive attached to configure it? ... new disk attached. I put the blank drive as #1 and ...

7/23/2012 11:12:55 AM