Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

How to extend Proxmox Local Container Storage

Posted on 29/05/201620/03/2023 IT Expert By IT Expert No Comments on How to extend Proxmox Local Container Storage
  1. Home
  2. Virtualization
  3. How to extend Proxmox Local Container Storage
extend-proxmox-local-container-instance

This explains how to extend the Local Container Storage of a Proxmox server. Stitching disks end to end to enable more containers to be stored locally on a Proxmox VE server. In this article, you will learn how to extend Proxmox Local Container Storage. Here is how to create a cluster in Proxmox VE. Below is the command to list disks “fdisk -l“. This command will not be enough for GPT partitions since PVE uses LVMs.

root@pve:~# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 10.7 GB, 10737418240 bytes

The following will yield the current status of disk devices and their partition details.

 cat /proc/partitions
root@pve:~# cat /proc/partitions
major minor #blocks name
8 0 10485760 sda
8 1 1007 sda1
8 2 130048 sda2
8 3 10354671 sda3
253 0 2359296 dm-0
253 1 1179648 dm-1
253 2 5636096 dm-2
root@pve:~#

Create the Physical Extent

To do this, please enter the command below.

root@pve:~# pvcreate /dev/sdb1
Physical volume "/dev/sdb1" successfully created

Now to check if it is available in the set of Physical Volumes.

root@pve:~# pvdisplay
 --- Physical volume ---
 PV Name /dev/sda2
 VG Name pve
 PV Size 1.82 TB / not usable 2.56 MB
 Allocatable yes
 PE Size (KByte) 4096
 Total PE 476803
 Free PE 1022
 Allocated PE 475781
 PV UUID I8G01N-slgw-6nBh-tjhy-EL6E-TJBC-p18pYS
"/dev/sdb1" is a new physical volume of "1.82 TB"
 --- NEW Physical volume ---
 PV Name /dev/sdb1
 VG Name
 PV Size 1.82 TB
 Allocatable NO
 PE Size (KByte) 0
 Total PE 0
 Free PE 0
 Allocated PE 0
 PV UUID hDyYtM-yJkZ-GKGa-Cva7-d73A-JKk6-xxxxxx

Note that the Physical Volume /dev/sdb1 does not have any Volume Group Name (VG Name) as yet.

Extend the Volume of Group

To extend the volume of the group. You may want to take a look at this link for more information. Please use the command below.

root@pve:~#vgextend "pve" /dev/sdb1
Volume group "pve" successfully extended

To display the volume of a group, please use the command “vgdisplay” as shown below.

root@pve:~#vgdisplay
 VG Name pve
 System ID
 Format lvm2
 Metadata Areas 2
 Metadata Sequence No 5
 VG Access read/write
 VG Status resizable
 MAX LV 0
 Cur LV 3
 Open LV 3
 Max PV 0
 Cur PV 2
 Act PV 2
 VG Size 3.64 TB
 PE Size 4.00 MB
 Total PE 953734
 Alloc PE / Size 475781 / 1.81 TB
 Free PE / Size 477953 / 1.82 TB
 VG UUID Tb9Ooy-N9vl-6fb0-3Px7-BX6w-yazp-lq5nVi
 The VG Size is now expanded (first highlight) and the Free PE (Physical Extents) / Size enlarged.

Resize the Logical Volume

Locate the volume of interest to allocate the available storage capacity. Actual Resizing the Logical Volume

lvresize -l 924296 /dev/mapper/pve-data

Result (Output)

Extending logical volume data to 3.53 TB. Logical volume data successfully resized.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:container, proxmox

Post navigation

Previous Post: Remove Packages from a Linux: Quick Guide
Next Post: Linux Error 13: Permission denied – Are you root

Related Posts

  • HyperV 1
    An error occurred while attempting to connect to the server: Check if the Virtual Machine Management service is running or you are not authorized to connect to this server Virtualization
  • VMware
    The validation process found problems on the server to which you want to install features, the features are not compatible with the current configuration of your server Virtualization
  • SCSI Controoler HyperV issue failed to start VM
    Failed to Power on with Error ‘A virtual machine disk support provider for the specified file was not found Virtualization
  • veeam backup for Proxmox VE
    Backup and Restore Proxmox VE virtual machines with Veeam Backup
  • MAP virtual disk error
    Install Workstation Pro 17: Fix failed to initialise library for mounting and unmounting virtual disks Virtualization
  • 87a26c60 0001 0004 0000 000001423515 w948 r1.77 fpx54.99 fpy56.04
    Administer LXC Containers: Easy Guide Virtualization

More Related Articles

HyperV 1 An error occurred while attempting to connect to the server: Check if the Virtual Machine Management service is running or you are not authorized to connect to this server Virtualization
VMware The validation process found problems on the server to which you want to install features, the features are not compatible with the current configuration of your server Virtualization
SCSI Controoler HyperV issue failed to start VM Failed to Power on with Error ‘A virtual machine disk support provider for the specified file was not found Virtualization
veeam backup for Proxmox VE Backup and Restore Proxmox VE virtual machines with Veeam Backup
MAP virtual disk error Install Workstation Pro 17: Fix failed to initialise library for mounting and unmounting virtual disks Virtualization
87a26c60 0001 0004 0000 000001423515 w948 r1.77 fpx54.99 fpy56.04 Administer LXC Containers: Easy Guide Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • microsoft confirms some pcs freeze after windows 10 2
    Information on BOOTP Vendor Extensions and DHCP Options Windows Server
  • GitLabrunner
    Install and Register GitLab Runner on Windows Version Control System
  • banner
    How to Integrate TestRail with Cypress Automation
  • Screenshot 2021 03 29 at 01.56.17
    How to prevent VLC player from reverting to the native video size on Mac Mac
  • VBR upgrade
    Upgrade Veeam Backup and Replication to version 12.2 Backup
  • image 16
    How to Fix Windows Error 0x80070057 Windows
  • windows update 03
    Fix Windows cannot check for updates in Windows 8, 7, and 10 Windows
  • banner 1
    How to Create Shared Folder in Windows Sandbox Virtualization

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,800 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.