On Wed, Jun 29, 2016 at 1:52 PM, Francesco Montesano
Hi all,
When the big update with the gcc6 arrived I did my usual dist-upgrade. Despite having at least 7Gb of free space on /, it took me 3 or 4 attempts to finish the installation because of "no space left on device". With a combination of removing some file in /tmp, logout-login and some waiting I managed to install all the packages and rebooted.
But then I started getting "no space left on device" for no apparent reason (I've also rebooted a couple of times in the meanwhile). I randomly get it e.g. when trying to install something with pip, doing tab-completion on bash or using sudo. Often after a few minutes the problem disappears by itself for some time. Today I was trying to create a python virtual environment and got this: OSError: [Errno 28] No space left on device: '/usr/tmp/tmpzrux9b_p'
I have no idea of what is going on, as I have plenty of space available. This is the situation now, but haven't changed much in the last week (I still haven't pull the last two updates):
~> df -h /dev/sdb2 41G 33G 7.2G 83% / [...] ~> btrfs filesystem df / Data, single: total=38.23GiB, used=31.09GiB System, single: total=32.00MiB, used=16.00KiB Metadata, single: total=1.75GiB, used=1.30GiB GlobalReserve, single: total=448.00MiB, used=0.00B
It may not be true that you have 7.2G free. What do you get for 'btrfs fi us /' ? What you have is 7.14GiB unused in data block groups. And 450MiB unused in metadata block groups. If the installation is very metadata centric, or contains many small files (less than about 15KiB) then those files get written in the metadata block group as an inline extent. There is a known enospc bug that results in errno -28. But it hasn't been fixed. http://www.spinics.net/lists/linux-btrfs/msg50945.html However I'm not certain you are being hit by this bug so it's better to report back btrfs fi us /. You could try 'btrfs balance start -dusage=25 /' which should free up one or more data block groups into unallocated space so that Btrfs can reallocate it as a metadata block group if needed. But again it's hard to say if that's enough space for this task. What is the estimated installation size? There are some other ways to find out what's going on, what block group is probably affecting this, but it means doing some iteration. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org