On 2017年06月24日 10:34, Marc MERLIN wrote:
On Fri, Jun 23, 2017 at 09:17:50AM -0700, Marc MERLIN wrote:
Thanks for looking at this.
I have applied your patch and I'm still re-running check in lowmem. It takes about 24H so I'll
post the full results when it's done.
Ok, here is the output of the check with btrfs-progs freshly synced from
git, including Lu's just added patch.
Obviously while I'm happy to give further debug info on why my filesystem is in that state and
while check --repair sees nothing to repair, suggestions on how to clean those warnings up, unless they are not going to affect filesystem operation, would be greatly appreciated :)
Thanks,
Marc
Thanks for the updated information. I'm sorry that the false alert make
you feel nervous.
ERROR: root 3862 EXTENT_DATA[18170706 4096] interrupt
ERROR: root 3862 EXTENT_DATA[18170706 16384] interrupt
ERROR: root 3862 EXTENT_DATA[18170706 20480] interrupt
ERROR: root 3862 EXTENT_DATA[18170706 135168] interrupt
ERROR: root 3862 EXTENT_DATA[18170706 1048576] interrupt
ERROR: errors found in fs roots
However, this looks like another problem. Could you dump this file tree
by the following command?
# btrfs-debug-tree -t 3862 <dev> | grep -C 10 18170706
--
Thanks,
Lu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
