No space left on device?

I’ve been getting errors lately like:

unable to write to /var/lib/sudo/ts/: No space left on device

So I learned how to check my disk space and the result of df -k:


Filesystem      1K-blocks     Used  Available Use% Mounted on
devtmpfs          4066960        0    4066960   0% /dev
tmpfs             4076148    35732    4040416   1% /dev/shm
tmpfs             4076148   195648    3880500   5% /run
tmpfs             4076148        0    4076148   0% /sys/fs/cgroup
/dev/sda2        41943040 40618656          0 100% /
/dev/sda2        41943040 40618656          0 100% /root
/dev/sda2        41943040 40618656          0 100% /.snapshots
/dev/sda2        41943040 40618656          0 100% /var
/dev/sda2        41943040 40618656          0 100% /opt
/dev/sda2        41943040 40618656          0 100% /srv
/dev/sda2        41943040 40618656          0 100% /boot/grub2/x86_64-efi
/dev/sda2        41943040 40618656          0 100% /usr/local
/dev/sda2        41943040 40618656          0 100% /tmp
/dev/sda2        41943040 40618656          0 100% /boot/grub2/i386-pc
/dev/sda3      3855030152 87705796 3767324356   3% /home
tmpfs              815228       36     815192   1% /run/user/1000

I don’t know what that’s about, all that used space. How do I correct this? Is that space taken up by installed packages or something?

Most likely your disk space has been eaten by btrfs snapshots. Run, if you can, yast - miscellaneous - snapper
Or show us output of


sudo snapper list

Hi , I seam to have the same problem

thread under hardware issued 2-3 days ago .

how can this happen , and how do I rescue the system?

using df -k results in

/dev/loops to 4 all blocks are used

I hope the administration reads this and can help

thanks and best regards

Actually, you might have the same problem, but if you notice, your output from df -k is totally different from the OP, so that would indicate either you are doing something different, or that it is NOT the same problem.

Therefore, jumping from thread to thread with seemingly-- but not quite – similar problems only results in completely confusing everyone involved and often results in the wrong things being done, potentially harming your system.

While you tagged onto this other person’s thread with a similar-sounding issue, you seem to have not followed the offered solutions in either thread properly, thus making things even more confusing.

Did you follow mrmazda’s advice to the letter? What was the result? Did you try the diagnostic command given here by Knurpht? What was the result?

You need to help the people who are trying to help you. Do those things carefully as instructed, then answer back with the results, wait for further instructions, then follow them.

That is the only way anyone can help you.

… and, stick to your own thread. Watch this one, perhaps try suggestions from here, or ask in your own thread if you should try them and follow the advice.

That said, as mentioned on the page that mrmazda pointed you to:

File system usage is usually checked by running the df command. However, on a Btrfs file system, the output of df can be misleading, because in addition to the space the raw data allocates, a Btrfs file system also allocates and uses space for metadata.

Consequently a Btrfs file system may report being out of space even though it seems that plenty of space is still available. In that case, all space allocated for the metadata is used up.

and also on that same page:

If Snapper is running for the Btrfs file system, the “No space left on device” problem is typically caused by having too much data stored as snapshots on your system. You can remove some snapshots from Snapper.

which is why Knurpht is asking for:

sudo snapper list

@frazer-bell : point taken !

… but that does not make me any wiser. I tried the latest suggestion using the write up and found commands like btrfs and snapper not working.

Thanks anyway