Thanks for the output.
At least for mprofile enospc error, the problem itself is very
straightforward, just unable to alloc tree block.
I'll check the codes to see if we can improve it, by finding out why we
can't alloc a new chunk to resolve the problem.
But I'm still a little concerned about the dprofile case, as this time,
dprofile doesn't trigger a ENOSPC and my debug info is not triggered.
Thanks,
Qu
Marc Haber wrote on 2016/03/01 17:16 +0100:
Hi,
On Tue, Mar 01, 2016 at 04:13:35PM +0800, Qu Wenruo wrote:
Oh, I'm sorry that the output is not necessary, it's better to use the newer
patch:
https://patchwork.kernel.org/patch/8462881/
With the newer patch, you will need to use enospc_debug mount option to get
the debug information.
I'll copy the log this time in the body of the message so that it gets
through to the list. Let me know if you'd prefer an attachment.
This time, I didn't see the busy kernel threads, and I now see ENOSPC
during the mprofiles part of the manual balance.
Hope this helps.
Greetings
Marc
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
