Ubuntu: 12.04 LTS
\nVMware ESXi: 5.5<\/p>\n
I wanted increase the store on one partition by 100GB to 250GB on a system and minimize down time. I was almost able to pull it off. I need one quick reboot to get the new size to show up.<\/p>\n
With the system up, I used the vSphere client and modifed the size of the disk.<\/p>\n
root@myhostname~:# df -h
\nFilesystem Size Used Avail Use% Mounted on
\n\/dev\/mapper\/vg_myhostname_subdir-lv_subdir 148G<\/strong> 125G 16G 90% \/mountpt\/subdir<\/p><\/blockquote>\nroot@myhostname~:# mount | grep subdir
\n\/dev\/mapper\/vg_myhostname_subdir-lv_subdir on \/mountpt\/subdir type ext4<\/strong> (rw)<\/p><\/blockquote>\nroot@myhostname~:# fdisk -l <\/p>\n
Disk \/dev\/sde: 161.1 GB, 161061273600<\/strong> bytes
\n255 heads, 63 sectors\/track, 19581 cylinders, total 314572800 sectors
\nUnits = sectors of 1 * 512 = 512 bytes
\nSector size (logical\/physical): 512 bytes \/ 512 bytes
\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes
\nDisk identifier: 0x00000000<\/p>\nDisk \/dev\/sde doesn’t contain a valid partition table<\/p><\/blockquote>\n
Scan for new hardware or changes:<\/p>\n
root@myhostname~:# echo “- – -” > \/sys\/class\/scsi_host\/host0\/scan
\nroot@myhostname~:# echo “- – -” > \/sys\/class\/scsi_host\/host1\/scan
\nroot@myhostname~:# echo “- – -” > \/sys\/class\/scsi_host\/host2\/scan <\/p><\/blockquote>\nStill didn’t show up with the new size:<\/p>\n
root@myhostname~:# pvdisplay
\n — Physical volume —
\n PV Name \/dev\/sde
\n VG Name vg_myhostname_subdir
\n PV Size 150.00 GiB \/ not usable 4.00 MiB
\n Allocatable yes (but full)
\n PE Size 4.00 MiB
\n Total PE 38399
\n Free PE 0
\n Allocated PE 38399
\n PV UUID dkK9oP-XQq2-p2CM-BVBZ-pv0r-J9cP-Hnc0UB<\/p><\/blockquote>\nI rebooted at this point.<\/p>\n
root@myhostname:~# fdisk \/dev\/sde
\nDevice contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
\nBuilding a new DOS disklabel with disk identifier 0xeeb3e856.
\nChanges will remain in memory only, until you decide to write them.
\nAfter that, of course, the previous content won’t be recoverable.<\/p>\nWarning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)<\/p>\n
Command (m for help): p<\/p>\n
Disk \/dev\/sde: 268.4 GB, 268435456000<\/strong> bytes
\n255 heads, 63 sectors\/track, 32635 cylinders, total 524288000 sectors
\nUnits = sectors of 1 * 512 = 512 bytes
\nSector size (logical\/physical): 512 bytes \/ 512 bytes
\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes
\nDisk identifier: 0xeeb3e856<\/p>\nDevice Boot Start End Blocks Id System<\/p>\n
Command (m for help): quit<\/p><\/blockquote>\n
root@myhostname:~# pvdisplay
\n — Physical volume —
\n PV Name \/dev\/sde
\n VG Name vg_myhostname_subdir
\n PV Size 150.00 GiB \/ not usable 4.00 MiB
\n Allocatable yes (but full)
\n PE Size 4.00 MiB
\n Total PE 38399
\n Free PE 0
\n Allocated PE 38399
\n PV UUID dkK9oP-XQq2-p2CM-BVBZ-pv0r-J9cP-Hnc0UB<\/p><\/blockquote>\nResize physical volume to reflect the new size:<\/p>\n
root@myhostname:~# pvresize \/dev\/sde
\n Physical volume “\/dev\/sde” changed
\n 1 physical volume(s) resized \/ 0 physical volume(s) not resized<\/p><\/blockquote>\nroot@myhostname:~# pvdisplay \/dev\/sde
\n — Physical volume —
\n PV Name \/dev\/sde
\n VG Name vg_myhostname_subdir
\n PV Size 250.00 GiB \/ not usable 3.81 MiB<\/strong>
\n Allocatable yes
\n PE Size 4.00 MiB
\n Total PE 63999
\n Free PE 25600
\n Allocated PE 38399
\n PV UUID dkK9oP-XQq2-p2CM-BVBZ-pv0r-J9cP-Hnc0UB<\/p><\/blockquote>\nInterestingly, the volume group updated with the new size:<\/p>\n
root@myhostname:~# vgdisplay
\n — Volume group —
\n VG Name vg_myhostname_subdir
\n System ID
\n Format lvm2
\n Metadata Areas 1
\n Metadata Sequence No 3
\n VG Access read\/write
\n VG Status resizable
\n MAX LV 0
\n Cur LV 1
\n Open LV 1
\n Max PV 0
\n Cur PV 1
\n Act PV 1
\n VG Size 250.00 GiB<\/strong>
\n PE Size 4.00 MiB
\n Total PE 63999
\n Alloc PE \/ Size 38399 \/ 150.00 GiB
\n Free PE \/ Size 25600 \/ 100.00 GiB
\n VG UUID QNgKYt-ueHo-hq54-kvWB-HRcd-3Guq-yfBwhu<\/p><\/blockquote>\nHowever, the logical volume did not:<\/p>\n
root@myhostname:~# lvdisplay
\n — Logical volume —
\n LV Name \/dev\/vg_myhostname_subdir\/lv_subdir
\n VG Name vg_myhostname_subdir
\n LV UUID D4xZEe-yAfH-pJoH-51Na-5l2B-Baqu-b37tOw
\n LV Write Access read\/write
\n LV Status available
\n # open 1
\n LV Size 150.00 GiB<\/strong>
\n Current LE 38399
\n Segments 1
\n Allocation inherit
\n Read ahead sectors auto
\n – currently set to 256
\n Block device 252:1<\/p><\/blockquote>\nSo, I had to extend it:<\/p>\n
root@myhostname:~# lvextend \/dev\/vg_myhostname_subdir\/lv_subdir \/dev\/sde
\n Extending logical volume lv_subdir to 250.00 GiB<\/strong>
\n Logical volume lv_subdir successfully resized<\/p><\/blockquote>\nroot@myhostname:~# lvdisplay
\n — Logical volume —
\n LV Name \/dev\/vg_myhostname_subdir\/lv_subdir
\n VG Name vg_myhostname_subdir
\n LV UUID D4xZEe-yAfH-pJoH-51Na-5l2B-Baqu-b37tOw
\n LV Write Access read\/write
\n LV Status available
\n # open 1
\n LV Size 250.00 GiB<\/strong>
\n Current LE 63999
\n Segments 1
\n Allocation inherit
\n Read ahead sectors auto
\n – currently set to 256
\n Block device 252:1<\/p><\/blockquote>\nNow, to resize the filesystem:<\/p>\n
root@myhostname:~# resize2fs \/dev\/mapper\/vg_myhostname_subdir-lv_subdir<\/strong>
\nresize2fs 1.42 (29-Nov-2011)
\nFilesystem at \/dev\/mapper\/vg_myhostname_subdir-lv_subdir is mounted on \/mountpt\/subdir; on-line resizing required
\nold_desc_blocks = 10, new_desc_blocks = 16
\nThe filesystem on \/dev\/mapper\/vg_myhostname_subdir-lv_subdir is now 65534976 blocks long.<\/p><\/blockquote>\nSuccess:<\/p>\n
root@myhostname:~# df -h
\nFilesystem Size Used Avail Use% Mounted on
\n\/dev\/mapper\/vg_myhostname_subdir-lv_subdir 247G<\/strong> 125G 110G 54% \/mountpt\/subdir<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"Ubuntu: 12.04 LTS VMware ESXi: 5.5 I wanted increase the store on one partition by 100GB to 250GB on a system and minimize down time. I was almost able to pull it off. I need one quick reboot to get the new size to show up. With the system up, I used the vSphere client [&hellip<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[438,132,33,303],"class_list":["post-1464","post","type-post","status-publish","format-standard","hentry","category-documentation","tag-resize","tag-ubuntu","tag-vmware","tag-volume"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1464","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1464"}],"version-history":[{"count":5,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1464\/revisions"}],"predecessor-version":[{"id":1469,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1464\/revisions\/1469"}],"wp:attachment":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1464"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1464"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}