On Sat, Mar 12, 2016 at 12:57 PM, Marc Haber <mh+linux-bt...@zugschlus.de> wrote: > On Sat, Mar 05, 2016 at 12:34:09PM -0700, Chris Murphy wrote: >> Something is happening with the usage of this file system that's out >> of the ordinary. This is the first time I've seen such a large amount >> of unused metadata allocation. And then for it not only fail to >> balance, but for the allocation amount to increase is a first. So >> understanding the usage is important to figuring out what's happening. >> I'd file a bug and include as much information on how the fs got into >> this state as possible. And also if possible make a btrfs-image using >> the proper flags to blot out the filenames for privacy. And what >> btrfs-progs tools were used to create this file system. Etc. > > https://bugzilla.kernel.org/show_bug.cgi?id=114451 > > Please advise if there is something missing.
No enospc_debug mount option used for kernel messages. And no indication you applied Qu's patch mentioned on March 1 to get more info with enospc_debug mount: >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. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
