From: cwillu <cwillu@cwillu.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Andreas Bauer <ab@voltage.de>, linux-btrfs@vger.kernel.org
Subject: Re: Kernel 2.6.36 btrfs csum bugreport
Date: Mon, 1 Nov 2010 05:02:10 -0600 [thread overview]
Message-ID: <AANLkTinjCa_7cDuY0AMypswssN4L73WMffuA6-mEWgde@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim3QfhFVvPaiKMSJPSjuRhG89=+DH63NsJf+SfH@mail.gmail.com>
On Mon, Nov 1, 2010 at 4:55 AM, Daniel J Blueman
<daniel.blueman@gmail.com> wrote:
> On 1 November 2010 00:35, Andreas Bauer <ab@voltage.de> wrote:
>> So I conclude that these messages are faulty because data is read co=
rrectly.
>> =A0In addition, when you have more than one btrfs you cannot see fro=
m the message
>> =A0which fs it is refering to.
>>
>> =A0Is this a raid1 or a dup array?
>>
>> No, plain vanilla partition on physical hard disk. Btrfs was made wi=
th the command "mkfs.btrfs /dev/sdc1" no extra arguments.
>
> By default, metadata is duplicated, thus it could be that BTRFS is
> using the correct copy of the metadata after finding checksum errors
> in the first copy.
Ahhhhhhh, and that makes this make sense:
Andreas, have you checked which file(s) are giving the errors? if
not, you can use "find /whatever/mountpoint -xdev -inum 5098 -print"
to get the filename. And I would bet that it's small enough that it's
being inlined into the metadata block group, and therefore covered
under the default "dup" profile of that block group, which is why
you're getting the actual file data back.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-01 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 0:35 Kernel 2.6.36 btrfs csum bugreport Andreas Bauer
2010-11-01 10:55 ` Daniel J Blueman
2010-11-01 11:02 ` cwillu [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-07 15:37 Andreas Bauer
2010-11-01 10:39 Andreas Bauer
2010-10-31 12:55 Andreas Bauer
2010-10-31 22:15 ` cwillu
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=AANLkTinjCa_7cDuY0AMypswssN4L73WMffuA6-mEWgde@mail.gmail.com \
--to=cwillu@cwillu.com \
--cc=ab@voltage.de \
--cc=daniel.blueman@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).