#Cant update aur packages with yay

48 messages · Page 1 of 1 (latest)

jolly wadi
#

Hello i am having an issue when trying to update my packages via yay it says this

 -> error resetting ffdec-bin: fatal: sha1 file '/home/retro-hax/.cache/yay/ffdec-bin/.git/index.lock' write error. Out of diskspace

here is my df -h output

Filesystem      Size  Used Avail Use% Mounted on
dev              16G     0   16G   0% /dev
run              16G  1.5M   16G   1% /run
/dev/sdc2       112G   48G   63G  43% /
tmpfs            16G  2.1M   16G   1% /dev/shm
/dev/sdc2       112G   48G   63G  43% /.snapshots
/dev/sdc2       112G   48G   63G  43% /var/cache/pacman/pkg
/dev/sdc2       112G   48G   63G  43% /var/log
/dev/sdb1       916G  870G  3.5M 100% /home
/dev/sda1       3.6T  3.4T   75G  98% /mnt/Samsung4TB
tmpfs            16G  121M   16G   1% /tmp
/dev/sdc1       510M   72M  439M  15% /boot
tmpfs           3.2G  136K  3.2G   1% /run/user/1000
#

here is also df -hi output

Filesystem     Inodes IUsed IFree IUse% Mounted on
dev              4.0M   755  4.0M    1% /dev
run              4.0M  1.1K  4.0M    1% /run
/dev/sdc2           0     0     0     - /
tmpfs            4.0M     5  4.0M    1% /dev/shm
/dev/sdc2           0     0     0     - /.snapshots
/dev/sdc2           0     0     0     - /var/cache/pacman/pkg
/dev/sdc2           0     0     0     - /var/log
/dev/sdb1         59M  6.4M   52M   11% /home
/dev/sda1        233M  2.1M  231M    1% /mnt/Samsung4TB
tmpfs            1.0M   159  1.0M    1% /tmp
/dev/sdc1           0     0     0     - /boot
tmpfs            801K   414  801K    1% /run/user/1000
tame parrot
#

Your /home partition is full

jolly wadi
#

ugh anyway to clean it up?

#

cuz i cant really upgrdade to bigger drive

#

or like idk install yay stuff on a seperate drive

jolly wadi
#

okay so uh why does gparted say this then

image.png
tame parrot
#

df -h output math was already off but it still said 100% used

jolly wadi
#

hmmm

rain rose
#

There are tools that let you view what is taking up space

fast prawn
#

sudo dumpe2fs -h /dev/sdb1 | grep -F 'Reserved block count'

jolly wadi
fast prawn
#

Since reserving blocks for root is borderline useless on a home partition, might as well get those 5% back with sudo tune2fs -m 0 /dev/sdb1

jolly wadi
jolly wadi
fast prawn
#

sdb1 sorry lmao

jolly wadi
# fast prawn sdb1 sorry lmao 
$ sudo dumpe2fs -h /dev/sdb1 | grep -F Free
dumpe2fs 1.47.0 (5-Feb-2023)
Free blocks:              12217806
Free inodes:              54350773
fast prawn
# jolly wadi uh what does it do?

when you format a new ext4 filesystem, the default options reserve 5% of the free blocks for the root user. This is so that in the case your disk fills up, system daemons have some space on disk to keep storing important logs.

#

This is somewhat useful on the root partition, where the system actually stores logs. But on a home partition, where there's basically only files owned by other users, there's no point on reserving blocks for root

jolly wadi
#

but thats not needed on a seperate drive for /home

fast prawn
jolly wadi
#

shall i still keep a backup in case?

fast prawn
#

that command sets the reserved blocks for root to 0% (none) for that partition

fast prawn
#

it doesn't touch any data

jolly wadi
#

ah oki

#

also this is probably right

$ sudo tune2fs -m 0 /dev/sdb1
tune2fs 1.47.0 (5-Feb-2023)
Setting reserved blocks percentage to 0% (0 blocks)
fast prawn
#

those 5% reserved blocks are just a number stored on the superblock. once the kernel detects the fs is 95% full it stops allowing users other than root to allocate blocks

jolly wadi
#

ah alright

fast prawn
jolly wadi
#

50GB now

#

good

fast prawn
jolly wadi
#

instead of the ~3GB i had earlier

fast prawn
#

which means you can expand existing files but not create new ones (or create any new directories, symlinks or hardlinks either)

#

if you remove the grep part you can see more generally useful information

#

ext4 is pretty fun

#

also, sudo pacman -S ncdu

#

it shows relative disk usage and sorts it so you can catch huge files you can probably delete

jolly wadi
fast prawn
#

when you run out of blocks you can create as many files as you want

#

as long as they're empty lmao

#

when you run out of blocks, you can also do any filesystem operations that don't require new blocks, such as overwriting or truncating files

#

you can also usually still move files around if your directories don't have too many files

jolly wadi
#

ah alright