permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 43b447f2caf5469e8e8903a05c334753b105edff
parent 06ddcd53b58cffea2c9a3c0fc5ded89c86f7f6ed
Author: spacehobo <spacehobo@web>
Date:   Tue,  5 May 2026 12:13:46 +0200

documenting filesystem shenanigans from this morning.

Diffstat:
Meik.mdwn | 10++++++++++
1 file changed, 10 insertions(+), 0 deletions(-)

diff --git a/eik.mdwn b/eik.mdwn @@ -9,6 +9,16 @@ ssh config Port 22 IdentityFile ~/.ssh/<ssh-private-key> +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 + +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 ----------------