On 10/9/2014 12:13 AM, Liu Bo wrote:
sudo ./btrfs inspect-internal logical-resolve -v 58464632832 /
$ sudo ./btrfs inspect-internal logical-resolve -v 58464632832 /
ioctl ret=0, total_size=4096, bytes_left=4080, bytes_missing=0, cnt=0,
missed=0
I also tried -P and -s 100000000 ....
Also did this:
$ sudo ./btrfs-map-logical -l 58464632832 -o /tmp/58464632832 /dev/sdf3
mirror 1 logical 58464632832 physical 1536393216 device /dev/sdg3
mirror 2 logical 58464632832 physical 58464632832 device /dev/sdf3
And looked at the 4k block. strings doesn't show anything useful: +V0T"
File doesn't recognize it as anything particular.
Weird.
I have one other clue which I think is irrelevant. I had another error
on a different drive/different fs and it turned out to be the vmem file
for a virtual machine under vmware workstation. I deleted the file
since it was just the memory image and the error went away. It was easy
to map the bad block to the file from dmesg and the inode. I may have
also created a vm at some point on this drive we're looking at now and
then moved it. So I think that information is not relevant... but maybe
you've seen this before.
--
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
