Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2012 05:40 AM
09-27-2012 05:40 AM
hi All,
I wonder to enlarge the "/" partition (on /dev/vg00/lvol3) on an inactive image of the system disk, bringing it from the actual 800 Mb to (at least) 1 Gb. But this partition should reside on contiguous blocks. I should probably use "pvmove" to move the actual /dev/vg00/lvol4 partition at the end (or at least in the first free blocks found) of the disk, and then enlarge the "/" partition on the newly acquired free blocks.
But I don't know how to do that ... can anybody please help me ?
That's the situation of the (unmounted) disk.
# vgdisplay -v /dev/drd00
--- Volume groups ---
VG Name /dev/drd00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4384
VGDA 2
PE Size (Mbytes) 32
Total PE 4374
Alloc PE 1642
Free PE 2732
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/drd00/lvol1
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 64
Allocated PE 64
Used PV 1
LV Name /dev/drd00/lvol3
LV Status available/syncd
LV Size (Mbytes) 800
Current LE 25
Allocated PE 25
Used PV 1
LV Name /dev/drd00/lvol4
LV Status available/syncd
LV Size (Mbytes) 12256
Current LE 383
Allocated PE 383
Used PV 1
LV Name /dev/drd00/lvol5
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 375
Allocated PE 375
Used PV 1
LV Name /dev/drd00/lvol6
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 32
Allocated PE 32
Used PV 1
LV Name /dev/drd00/lvol7
LV Status available/syncd
LV Size (Mbytes) 5152
Current LE 161
Allocated PE 161
Used PV 1
LV Name /dev/drd00/lvol8
LV Status available/syncd
LV Size (Mbytes) 9024
Current LE 282
Allocated PE 282
Used PV 1
LV Name /dev/drd00/swap
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 320
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c3t2d0
PV Status available
Total PE 4374
Free PE 2732
Autoswitch On
Proactive Polling On
Thank you in advance
Enrico
Solved! Go to Solution.
- Tags:
- pvmove
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2012 06:30 AM
09-27-2012 06:30 AM
Re: pvmove
Never done this so far, but this could probably work:
# pvmove -p -n /dev/vg00/lvol4 /dev/dsk/c3t2d0 /dev/dsk/c3t2d0
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2012 06:43 AM
09-27-2012 06:43 AM
Re: pvmove
Sorry, I forgot to specify I'm at 11.23 release. At 11v3 there are other (useful) options of "pvmove", like the exact specifications of the disk sectors implied in the physical move.
Thank you Torsten, I will try lately your suggestion.
Enrico
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2012 06:58 AM
09-27-2012 06:58 AM
Re: pvmove
mirror lvol4, then remove the original
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2012 07:55 AM
09-27-2012 07:55 AM
Re: pvmove
Hi,
I, too, wouls suppose mirroring lvol4 or creatin a new one, copying it and - after it is sure, that the copy works, delete the original.
Another way might be to move some content of the present lvol3 to a new filesystem, that is not restricted by anc continous tag and that contains data, that needs not to be available at system boot. May be your /tmp or var directories are right now part of the / fielsystem. You could create seperate filesystems for those directories.
Bye
Ralf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2012 02:21 AM
09-28-2012 02:21 AM
Re: pvmove
I'm afraid but it seems that pvmove does not work on the same disk.
# pvmove -n /dev/vg00/lvol4 /dev/dsk/c3t2d0 /dev/dsk/c3t2d0
Usage: pvmove
[-A Autobackup]
[-n LogicalVolumeName]
SourcePhysicalVolumePath [ DestinationPhysicalVolumePath... | DestinationPhysicalVolumeGroupName... ]
or
pvmove [-A Autobackup] SourcePhysicalVolumePath[:0] [ DestinationPhysicalVolumePath... | DestinationPhysicalVolumeGroupName... ]
"SourcePhysicalVolumePath": The source physical volume is also in the set of
destination physical volume(s).
Enrico
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2012 06:11 AM
09-28-2012 06:11 AM
SolutionHi,
Finally did.
What I've done:
1) boot from the DRD image (created with the Dynamic Root Disk utility)
2) create a new partition on the "new", actual system disk: /dev/vg00/lvol9 mounted on /home_new
3) cd / , cp -rp home home_new
4) unmount /home (/dev/vg00/lvol4)
5) destroy /dev/vg00/lvol4
6) unmount /home_new, edit /etc/fstab to mount /dev/vg00/lvol9 on /home
7) reboot from the "old" system disk
8) extend /dev/drd00/lvol3 (lvextend -L 1536 /dev/drd00/lvol3) -> now it works !
9) extendfs -F vxfs /dev/drd00/lvol3
10) lvlnboot -r lvol3 /dev/drd00
11) reboot from the "new" system disk
Now the "/" partition has been enlarged enough to perform the system upgrade.
Thank you all for your time
Enrico