Re: 4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free?

2017-10-22 Thread Vladimir Panteleev
On 2017-10-19 12:14, Martin Raiber wrote: You could also mount with "enospc_debug" to give the devs more infos about this issue. I am having more ENOSPC issues with 4.9.x than with the latest 4.14. Here is the dmesg output with -o enospc_debug, hopefully it will be useful for someone:

Re: 4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free?

2017-10-19 Thread Martin Raiber
On 19.10.2017 10:16 Vladimir Panteleev wrote: > On Tue, 17 Oct 2017 16:21:04 -0700, Duncan wrote: >> * try the balance on 4.14-rc5+, where the known bug should be fixed > > Thanks! However, I'm getting the same error on > 4.14.0-rc5-g9aa0d2dde6eb. The stack trace is different, though: > > Aside

Re: 4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free?

2017-10-19 Thread Vladimir Panteleev
On Tue, 17 Oct 2017 16:21:04 -0700, Duncan wrote: * try the balance on 4.14-rc5+, where the known bug should be fixed Thanks! However, I'm getting the same error on 4.14.0-rc5-g9aa0d2dde6eb. The stack trace is different, though: [25886.024757] BTRFS: Transaction aborted (error -28)

Re: 4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free?

2017-10-17 Thread Duncan
Vladimir Panteleev posted on Tue, 17 Oct 2017 17:19:45 + as excerpted: > I'm experiencing some issues with a btrfs filesystem - mounting and > other operations taking forever, a balance that takes hours to start and > never completes (due to the error in the subject line), and I've also >

4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free?

2017-10-17 Thread Vladimir Panteleev
Hi, I'm experiencing some issues with a btrfs filesystem - mounting and other operations taking forever, a balance that takes hours to start and never completes (due to the error in the subject line), and I've also seen the NULL pointer dereference in free_reloc_roots which Naohiro Aota