I have a Leap 42.3 system that was working fine. I started a zypper dup, and part way through, it started complaining that there was no space on /var/log. This is not true. There are a couple of GB free on the /var file system. Still, I deleted a couple of log files to see what happened. The files deleted fine, and the free space as reported by df increased ad expected. However, I cannot write anything to /var/log. If I just try to touch a new file it complains that there is no free space on the device. I have rebooted, but the problem persists. The setup is btrfs as Leap 42.3 set up. Until this, all has been working great. When you cannot write to /var/log or such places, lots of system stuff no longer starts. So even though I can log in, all is rather basic. If this was the old ext4, I would run fsck. I have to admit that the options with btrfs are less clear to me. I have tried the suggestions here: https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_o... When I run "btrfs fi balance start -dusage=5 /mount/point", no chunks are relocated. So I tried increasing the usage= value. When I hit 70, it complains that there is no space left on the device. So this seems not to be able to solve the problem. I cannot get it re reallocate a chunk. I have also checked here: https://www.suse.com/documentation/sles11/stor_admin/data/trbl_btrfs_volfull... It suggests pretty much the same thing. I have not tried removing a snapshot. I would only expect that to help when there is actually no free space. But that is not the case. I do not want to destroy this system It is my work system. I'm open to suggestions. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org