On Sun, Sep 03, 2017 at 12:30:07AM +0000, Josef Bacik wrote:
> My bad, I forgot I don't dynamically allocate the stack trace space so my
> patch did nothing, I blame the children for distracting me. I've dropped
> allocating the action altogether for the on disk stuff, that should
> dramatically reduce the memory usage. You can just do a git pull since I
> made a new commit. You are mounting with -o ref_verify on only the one fs
> right? Give this a try and if it still doesn't work we can try a stripped
> down version that doesn't build the initial tree and just hope that the
> problem exists in allocating a new block and not modifying the refs for an
> existing block. Thanks,
Good news, this time it booted without crashing on OOM.
I'll now get to see how it runs and hopefully it won't crash due to
other problems in 4.13
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
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
