this post was submitted on 30 May 2024
25 points (96.3% liked)

Selfhosted

40329 readers
401 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hey everyone, I'm currently using proxmox to virtualize my OPNsense and another VM. Today when I went to create a third VM, everything crashed with I/O errors, and I realized my local-lvm was out of space. This was odd to me since I have a 1TB drive and only have two small VMs.

To my surprise, proxmox is only using 100GB of my disk. Can someone please guide me on how I can fix this without having to reinstall proxmox? I would prefer to have my OPNsense VM running while I fix this. Here are some diagnostics to help. Thanks

https://pastebin.com/1N7fwmYy

you are viewing a single comment's thread
view the rest of the comments
[–] AbidanYre@lemmy.world 3 points 5 months ago* (last edited 5 months ago) (3 children)

Edit: nevermind, sda3 is already being used. The lv group needs to be embiggened.

[–] notdeadyet@lemmy.dbzer0.com 3 points 5 months ago (1 children)

Would you know how I would go about doing that?

[–] AbidanYre@lemmy.world 7 points 5 months ago (1 children)

I've done it before, but there's always a lot of googling involved. I think a combination of vgdisplay and vgextend may help: https://www.redhat.com/sysadmin/resize-lvm-simple

If sda3 is really <100GB it gets a lot scarier but is likely still doable.

I'm not a fan of Proxmox's partitioning scheme and usually use a separate drive for the OS and the VMs because of this exact scenario.

[–] notdeadyet@lemmy.dbzer0.com 18 points 5 months ago* (last edited 5 months ago)

That led me in the right direction!

Fixed it with:

pvresize /dev/sda3
lvresize --extents +100%FREE --resizefs /dev/pve/data

Thank you!

load more comments (1 replies)