On Mon, Jan 30, 2017 at 06:07:01PM +0530, Lakshmipathi.G wrote: > > > > 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 > > > > Thanks for the details. This owner number looked different from other > owner ids, so wanted to check on the same, now understood.
Recently, in the commit 6f6b643e44ef7, the known tree ids are printed as the small negative numbers. We can also do that in progs, however we'd need some tricks so we don't duplicate all format strings one with %llu and one with %lld. Something like format: "%s%llu" values: id > LAST_FREE ? "-" : "" id > LAST_FREE ? 2^64 - id : id and hidden in helpers etc. I don't think we should replace all references to tree ids with the symbolic names as they're used in keys so searching for the numeric value in the dump output would miss something or make the regexp more complicated. I won't object against making the tree id output format selectable by option though. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
