On Mon, Jan 13, 2020 at 7:16 PM Christian Kujau <lists@xxxxxxxxxxxxxxx> wrote: > > On Mon, 13 Jan 2020, Chris Murphy wrote: > > This is the latest patchset as of about a week ago, and actually I'm > > not seeing it in 5.5rc6. A tested fix may not be ready yet. > > https://patchwork.kernel.org/project/linux-btrfs/list/?series=223921 > > > > Your best bet is likely to stick with 5.4.10 and just use mount option > > metadata_ratio=1. This won't cause some other weird thing to happen. > > I have remounted the file system with that option set when it was still > running, but it didn't do anything (as expected I'd assume), its usage was > still at 100 percent. > > Now I had a chance to reboot the system (with that option set), but usage > was still at 100%, so I ran "btrfs balance" once more (although you > recommended against it :)) and a reboot later everything seems "normal" > again. > > Thanks for the explanations and hints. I must admit it's kinda surprising > to me that these ENOSPC errors are still happening with btrfs, I somehow > assumed that these kinks had been ironed out by now. But as you said, this > may have re-appeared with 5.4 and it's not a big deal for me right now, so > I can live with the mount option set and wait for 5.5 to be released :-) If you have a bugzilla account file a bug. You can put me on the cc, use bugzilla@ instead of lists@, and then you'll get a notification when this is fixed in a future Fedora kernel. You can just wipe out the whole template and copy/paste your first email in it. That's enough info I think. -- Chris Murphy
