Chris Mason wrote: >> That's all. Reading one of the damaged file actually returned >> "Input/output error" - probably it tried to read beyond end-of-device. I >> had to kill this file (practical testing means that to continue to use >> my notebook normally I had to nuke the damaged file and get intact >> copies). The "no such file except in readdir" is still there right now. > > Ok, btrfsck will give us more output when it finishes, but it hasn't > finished. It would help to use btrfs-image to send us a coyp of the > metadata so we can fix the btrfsck bug.
I have a 74M compressed btrfs-image of a partition with a ghost file (I sent btrfsck logs earlier). Would they be of any use in debugging handling of such situations? If yes - how should I transmit the image file? How can I kill the ghost file? -- 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
