From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>,
linux-btrfs@vger.kernel.org
Subject: Re: Fresh Raid-1 setup, dump-tree shows invalid owner id
Date: Mon, 30 Jan 2017 12:43:07 +0100 [thread overview]
Message-ID: <006ecc84-52fb-2b09-0e47-317fa018e9f9@mendix.com> (raw)
In-Reply-To: <20170130015416.GA5619@giis.co.in>
On 01/30/2017 02:54 AM, Lakshmipathi.G 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?
Yes, the owner is the number of the tree.
DATA_RELOC_TREE is -9, but then unsigned 64 bits.
>>> -9 + 2**64
18446744073709551607L
So the result is a number that's close to the max or 64 bits.
You can find those numbers in the kernel source in
include/uapi/linux/btrfs_tree.h
e.g.:
#define BTRFS_DATA_RELOC_TREE_OBJECTID -9ULL
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-01-30 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 1:54 Fresh Raid-1 setup, dump-tree shows invalid owner id Lakshmipathi.G
2017-01-30 11:34 ` Lakshmipathi.G
2017-01-30 11:43 ` Hans van Kranenburg [this message]
2017-01-30 12:37 ` Lakshmipathi.G
2017-03-13 17:34 ` David Sterba
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=006ecc84-52fb-2b09-0e47-317fa018e9f9@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=lakshmipathi.g@giis.co.in \
--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).