No idea; can you grab /proc/slabinfo and /proc/meminfo every minute or so until it oom kills trinity? Maybe that will give us a hint of at least where the memory is getting consumed. It could be the extent status tree cache, for which the need for a better shrinker is a known bug that we're working on, but that's just a wild guess. Thanks, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
