From: Christoph Weber <Christoph.Weber@xpecto.com>
To: "'pve-user@lists.proxmox.com'" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] pve-user Digest, Vol 172, Issue 2
Date: Tue, 12 Jul 2022 06:39:20 +0000 [thread overview]
Message-ID: <0efcc23b85794a6a88f01fd3f473f61c@xpecto.com> (raw)
In-Reply-To: <mailman.3.1657533603.22223.pve-user@lists.proxmox.com>
> Did I miss something, or is it really safe to destroy pve/data safely?
As nobody cried out "Don'nt", I took all my courage together and tried my best:
First I deactivated pve/data trough:
lvchange -an /dev/mapper/pve-data
After nothing bad did happen, I removed it
lvremove pve/data
Then I could extend pve/root by 90% oft he now free space
lvextend -l+90%FREE pve/root
and resized the fs
resize2fs /dev/pve/root
Everything still is fine until now 😉
parent reply other threads:[~2022-07-12 6:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.3.1657533603.22223.pve-user@lists.proxmox.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0efcc23b85794a6a88f01fd3f473f61c@xpecto.com \
--to=christoph.weber@xpecto.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.