On Mon, Nov 1, 2010 at 4:55 AM, Daniel J Blueman <daniel.blueman@xxxxxxxxx> wrote: > On 1 November 2010 00:35, Andreas Bauer <ab@xxxxxxxxxx> wrote: >> So I conclude that these messages are faulty because data is read correctly. >> In addition, when you have more than one btrfs you cannot see from the message >> which fs it is refering to. >> >> Is this a raid1 or a dup array? >> >> No, plain vanilla partition on physical hard disk. Btrfs was made with 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
