From: Rich Rauenzahn <rich@shroop.net>
To: bo.li.liu@oracle.com
Cc: Rich Rauenzahn <rrauenza@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Two uncorrectable errors across RAID1 at same logical block?
Date: Thu, 09 Oct 2014 09:58:03 -0700 [thread overview]
Message-ID: <5436BE9B.90300@shroop.net> (raw)
In-Reply-To: <20141009071337.GA13470@localhost.localdomain>
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.
next prev parent reply other threads:[~2014-10-09 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 17:06 Two uncorrectable errors across RAID1 at same logical block? Rich Rauenzahn
2014-10-07 2:05 ` Liu Bo
2014-10-07 2:18 ` Rich Rauenzahn
2014-10-08 14:20 ` Liu Bo
2014-10-08 16:13 ` Rich Rauenzahn
2014-10-09 7:13 ` Liu Bo
2014-10-09 16:58 ` Rich Rauenzahn [this message]
2014-10-11 8:52 ` Liu Bo
2014-10-11 15:11 ` Rich Rauenzahn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5436BE9B.90300@shroop.net \
--to=rich@shroop.net \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rrauenza@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.