commit 7c269deca02458b9b5d8e4349f946298b3b3fabe
parent 43b447f2caf5469e8e8903a05c334753b105edff
Author: spacehobo <spacehobo@web>
Date: Wed, 6 May 2026 19:17:27 +0200
Updating current state now that I got the disk added to /
Diffstat:
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/eik.mdwn b/eik.mdwn
@@ -15,14 +15,16 @@ disk volumes
`eik` uses LVM, and we recently added 5G to `/var` before realising that that was nearly all of the disk space we'd been allocated. Growing the volume was as simple as:
sudo lvextend --size +5G --resizefs /dev/mapper/permacomputing--vg-var
- sudo lvextend --extents 100%FREE --resizefs /dev/mapper/permacomputing--vg-root
+ sudo lvextend --extents +100%FREE --resizefs /dev/mapper/permacomputing--vg-root
+
+The first attempt to grow `/` had a typo (missing the `+`), so we reached out and got more disk added (possibly `/dev/vda2`: `vda1` is `/boot` and `vda5` is the LVM pool). We will review our consumption needs after we complete more work, but we may want to return the space added on 6 May.
-Sadly we found that the second command only allowed an extra couple hundred megabytes to the already full `/`. Shrinking `/var` back down doesn't seem to work at present, as `e2fsck` doesn't accept that it's been unmounted.
upgrading debian
----------------
-We don't have enough space to upgrade debian mostly. Here are some tricks.
+We recently added space, which should make upgrades easier. Here are some tricks we developed when space on `/` was tight.
+
* Make sure all old linux kernels are removed. You can upgrade/reboot and then check with `uname -a`/`uname -rms` to see what you're running. Then use `dpkg --list | grep -E 'linux-image|linux-headers'` to identify the old ones and directly `apt remove ...`.
* Pay attention to what the `apt full-upgrade` disk space info is telling you. Check what you've got on the `/` partition with `df -h`. If you don't have enough, it won't work.
