On Mon, May 9, 2016 at 4:56 AM, Alejandro Vargas <a...@zener.es> wrote: > El Martes, 26 de abril de 2016 00:08:49 Chris Murphy escribió: >> On Mon, Apr 25, 2016 at 8:03 AM, Alejandro Vargas <a...@zener.es> wrote: > >> I suggest unmounting and running 'btrfs check' (without repair) and >> see if that gives any new information. > > I tried btrfs check but... see the result: > > # btrfs check /dev/sdb1 > Checking filesystem on /dev/sdb1 > UUID: cbfe8735-9f53-46f5-be7e-40f6a61a5506 > checking extents > Killed > > > I tried it several times with the same result.
If this is btrfs-progs 4.5.2 it's worth filing a bug. You can trivially use 'strace btrfs check /dev/sdb1' and attach the entire output to the bug report as a file (pasting it in the bug will be messy). More advanced would be to use something like valgrind on it, but only a dev would be able to tell you if it's helpful, I can't: valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes -v btrfs check /dev/sdb1 If it's not progs v.4.5.2 then I suggest upgrading and see if the problem still happens. -- 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
