At 01/20/2017 11:10 PM, Chris Murphy wrote:
On Thu, Jan 19, 2017 at 10:45 PM, Qu Wenruo <[email protected]> wrote:
Another file system, 15 minutes old with two mounts in its whole
lifetime, and only written with kernel 4.10-rc3 has over 30 lines of
varying numbers:
ERROR: root 257 EXTENT DATA[150134 11317248] prealloc shouln't have
datasum
That file system should have no preallocated extents (It's a clean
installation of Fedora Rawhide, using only rsync)
btrfs-debug-tree will help to make sure what is wrong.
6b187fa6.logs.tar.gz 20M
https://drive.google.com/open?id=0B_2Asp8DGjJ9SlRvZ2plNXVmTUU
That's the small recent one, generic content. The others are bigger,
and I should probably sanitize the filenames from debug-tree but can't
find in the archives how to do that. Is btrfs-image useful for this?
Normally, btrfs-image is the best format, as we can just test if the fix
is good or not directly on the image.
Not to mention btrfs-image has -s option to sanitize filenames. And
btrfs-image is normally a little smaller than debug tree output.
Thanks,
Qu
That's why lowmem mode is still not the default option.
The problem os original mode is, if you're checking a TB level fs and only 2
or 4G ram, then it's quite possible you ran out of memory and won't be able
to check the fs forever, more several than annoying.
Fair enough.
--
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
