From 4d24be52546d272f0f33263d8f89112ac3a6df4b Mon Sep 17 00:00:00 2001 From: taradiddles Date: Sun, 17 Jun 2018 17:43:09 +0300 Subject: [PATCH] use placeholder instead of fixed size + moved to proper location --- _tmp/issue-37.md => docs/configuration/shrink-volumes.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) rename _tmp/issue-37.md => docs/configuration/shrink-volumes.md (94%) diff --git a/_tmp/issue-37.md b/docs/configuration/shrink-volumes.md similarity index 94% rename from _tmp/issue-37.md rename to docs/configuration/shrink-volumes.md index 53d1a74..d4f81c6 100644 --- a/_tmp/issue-37.md +++ b/docs/configuration/shrink-volumes.md @@ -28,19 +28,21 @@ The instructions below show how to resize a Linux VM's private volume. For root Alternatively, you could setup a loop device in dom0 associated to largeVM's private volume and attach it to a running VM but this is outside the scope of this document (see `losetup` and `qvm-block`). -4. in tempVM, resize the attached volume (for instance to 2 GB): +4. in tempVM, resize the attached volume: ~~~ sudo e2fsck -f /dev/xvdi - sudo resize2fs /dev/xvdi 2G + sudo resize2fs /dev/xvdi ~~~ + (eg. `` = `2G` ; see `man resize2fs` for allowed formats). + 5. shutdown tempVM 6. in dom0, resize the lvm volume to the **SAME** size you used at step 4. (specifying a lower size than the underlying filesystem's size **will corrupt** the filesystem and either destroy some of your data or trigger filesystem exceptions when the filesystem tries to write at a location that doesn't exist): ~~~ - sudo lvresize -L2G /dev/qubes_dom0/vm-largeVM-private + sudo lvresize -L /dev/qubes_dom0/vm-largeVM-private ~~~