Raid1 is irrelevant, looks like this happen with simple case too. $./mkfs.btrfs tests/test.img $./btrfs-debug-tree tests/test.img possible issue with ./btrfs-debug-tree stdout? On Mon, Jan 30, 2017 at 7:24 AM, Lakshmipathi.G <lakshmipathi.g@xxxxxxxxxx> wrote: > After creating raid1: > $./mkfs.btrfs -f -d raid1 -m raid1 /dev/sda6 /dev/sda7 > > and using > $./btrfs inspect-internal dump-tree /dev/sda6 #./btrfs-debug-tree /dev/sda6 > > shows possible wrong value for 'owner'? > -- > checksum tree key (CSUM_TREE ROOT_ITEM 0) > leaf 29425664 items 0 free space 16283 generation 4 owner 7 > fs uuid 94fee00b-00aa-4d69-b947-347f743117f2 > chunk uuid 6477561c-cbca-45e4-980d-56727a8dc9d9 > data reloc tree key (DATA_RELOC_TREE ROOT_ITEM 0) > leaf 29442048 items 2 free space 16061 generation 4 owner 18446744073709551607 <<< owner id? > fs uuid 94fee00b-00aa-4d69-b947-347f743117f2 > chunk uuid 6477561c-cbca-45e4-980d-56727a8dc9d9 > -- > > or is that expected output? > > Cheers. > Lakshmipathi.G > -- > 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 -- 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
