On Sun, Jun 07, 2020 at 06:28:44PM +0800, Qu Wenruo wrote: > On 2020/6/7 下午6:00, Michał Mirosław wrote: > > On Sun, Jun 07, 2020 at 10:34:52AM +0200, Michał Mirosław wrote: > >> On Sun, Jun 07, 2020 at 03:35:36PM +0800, Qu Wenruo wrote: > >>> On 2020/6/7 下午1:12, Michał Mirosław wrote: > >>>> Dear btrfs developers, > >>>> > >>>> I just added a new disk to already almost full filesystem and tried to > >>>> enable raid1 for metadata (transcript below). > >>> May I ask for your per-disk usage? > >>> > >>> There is a known bug (but rare to hit) that completely unbalance disk > >>> usage can lead to unexpected ENOSPC (-28) error at certain critical code > >>> and cause the transaction abort you're hitting. > >>> > >>> If you have added a new disk to an almost full one, then I guess that > >>> would be the case... [...] > >>> If your disk layout fits my assumption, then the following patchset is > >>> worth trying: > >>> https://patchwork.kernel.org/project/linux-btrfs/list/?series=297005 > >> I'll give it a try. > > > > The series doesn't apply on 5.6.x nor 5.7.x. :( > > It's based on current David's misc-next branch: > https://github.com/kdave/btrfs-devel/tree/misc-next Thanks for the pointer. I'll try to backport this if I hit the problem again. Best Regards, Michał Mirosław
