On Mon, 13 Jan 2020, Chris Murphy wrote: > > Well, I received some ENOSPC notifications from various apps, so it was a > > real problem. > > Oh it's a real problem and a real bug. But the file system itself is OK. Ah, OK. Good to know. > > For now, the balancing "helped", but the fs still shows only 391 GB > > allocated from the 924 GB device: The first "balance start --full-balance /" finshed, with the following message, of course: ERROR: error during balancing '/': No space left on device But afterwards at least "df" was happy and reported 48% usage again. While writing the last email I started another "balance start --full-balance /" to balance the extents that could not be balanced before because the file system was at 100%. But this failed with the same message and now I'm back to square one: ============================================================= # btrfs filesystem df -h / Data, single: total=391.00GiB, used=386.38GiB System, single: total=32.00MiB, used=80.00KiB Metadata, single: total=2.00GiB, used=1.55GiB GlobalReserve, single: total=512.00MiB, used=0.00B # df -h / Filesystem Size Used Avail Use% Mounted on /dev/mapper/luks-root 825G 389G 0 100% / ============================================================= Sigh. I can't reboot right now, will do later on and will try another balance now. > A less janky option is to use 5.3.18, or grab 5.5.0-rc6 from koji. > I've been using 5.5.0 for a while for other reasons (i915 gotchas), > and the one Btrfs bug I ran into related to compression has been fixed > as of rc5. > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1428886 OK, thanks for the hint, I'll do that in a few hours when I'm able to reboot. Thanks, Christian. -- BOFH excuse #69: knot in cables caused data stream to become twisted and kinked
