2018-04-03 11:23:33 -06:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2007-06-12 07:07:21 -06:00
|
|
|
/*
|
|
|
|
|
* Copyright (C) 2007 Oracle. All rights reserved.
|
|
|
|
|
*/
|
|
|
|
|
|
2007-02-24 04:24:44 -07:00
|
|
|
#include "ctree.h"
|
|
|
|
|
#include "disk-io.h"
|
2007-05-02 13:53:43 -06:00
|
|
|
#include "print-tree.h"
|
2007-02-24 04:24:44 -07:00
|
|
|
|
2008-03-24 13:01:56 -06:00
|
|
|
static void print_chunk(struct extent_buffer *eb, struct btrfs_chunk *chunk)
|
|
|
|
|
{
|
|
|
|
|
int num_stripes = btrfs_chunk_num_stripes(eb, chunk);
|
|
|
|
|
int i;
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tchunk length %llu owner %llu type %llu num_stripes %d\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
btrfs_chunk_length(eb, chunk), btrfs_chunk_owner(eb, chunk),
|
|
|
|
|
btrfs_chunk_type(eb, chunk), num_stripes);
|
2008-03-24 13:01:56 -06:00
|
|
|
for (i = 0 ; i < num_stripes ; i++) {
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\t\tstripe %d devid %llu offset %llu\n", i,
|
2013-08-20 05:20:07 -06:00
|
|
|
btrfs_stripe_devid_nr(eb, chunk, i),
|
|
|
|
|
btrfs_stripe_offset_nr(eb, chunk, i));
|
2008-03-24 13:01:56 -06:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
static void print_dev_item(struct extent_buffer *eb,
|
|
|
|
|
struct btrfs_dev_item *dev_item)
|
|
|
|
|
{
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tdev item devid %llu total_bytes %llu bytes used %llu\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
btrfs_device_id(eb, dev_item),
|
|
|
|
|
btrfs_device_total_bytes(eb, dev_item),
|
|
|
|
|
btrfs_device_bytes_used(eb, dev_item));
|
2008-03-24 13:01:56 -06:00
|
|
|
}
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
static void print_extent_data_ref(struct extent_buffer *eb,
|
|
|
|
|
struct btrfs_extent_data_ref *ref)
|
|
|
|
|
{
|
2017-08-18 15:15:24 -06:00
|
|
|
pr_cont("extent data backref root %llu objectid %llu offset %llu count %u\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
btrfs_extent_data_ref_root(eb, ref),
|
|
|
|
|
btrfs_extent_data_ref_objectid(eb, ref),
|
|
|
|
|
btrfs_extent_data_ref_offset(eb, ref),
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
btrfs_extent_data_ref_count(eb, ref));
|
|
|
|
|
}
|
|
|
|
|
|
2014-07-02 11:20:48 -06:00
|
|
|
static void print_extent_item(struct extent_buffer *eb, int slot, int type)
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
{
|
|
|
|
|
struct btrfs_extent_item *ei;
|
|
|
|
|
struct btrfs_extent_inline_ref *iref;
|
|
|
|
|
struct btrfs_extent_data_ref *dref;
|
|
|
|
|
struct btrfs_shared_data_ref *sref;
|
|
|
|
|
struct btrfs_disk_key key;
|
|
|
|
|
unsigned long end;
|
|
|
|
|
unsigned long ptr;
|
|
|
|
|
u32 item_size = btrfs_item_size_nr(eb, slot);
|
|
|
|
|
u64 flags;
|
|
|
|
|
u64 offset;
|
2017-08-18 15:15:24 -06:00
|
|
|
int ref_index = 0;
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
|
2018-06-26 08:20:59 -06:00
|
|
|
if (unlikely(item_size < sizeof(*ei))) {
|
2018-06-26 07:57:36 -06:00
|
|
|
btrfs_print_v0_err(eb->fs_info);
|
|
|
|
|
btrfs_handle_fs_error(eb->fs_info, -EINVAL, NULL);
|
|
|
|
|
}
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
|
|
|
|
|
ei = btrfs_item_ptr(eb, slot, struct btrfs_extent_item);
|
|
|
|
|
flags = btrfs_extent_flags(eb, ei);
|
|
|
|
|
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\textent refs %llu gen %llu flags %llu\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
btrfs_extent_refs(eb, ei), btrfs_extent_generation(eb, ei),
|
|
|
|
|
flags);
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
|
2014-07-02 11:20:48 -06:00
|
|
|
if ((type == BTRFS_EXTENT_ITEM_KEY) &&
|
|
|
|
|
flags & BTRFS_EXTENT_FLAG_TREE_BLOCK) {
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
struct btrfs_tree_block_info *info;
|
|
|
|
|
info = (struct btrfs_tree_block_info *)(ei + 1);
|
|
|
|
|
btrfs_tree_block_key(eb, info, &key);
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\ttree block key (%llu %u %llu) level %d\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
btrfs_disk_key_objectid(&key), key.type,
|
|
|
|
|
btrfs_disk_key_offset(&key),
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
btrfs_tree_block_level(eb, info));
|
|
|
|
|
iref = (struct btrfs_extent_inline_ref *)(info + 1);
|
|
|
|
|
} else {
|
|
|
|
|
iref = (struct btrfs_extent_inline_ref *)(ei + 1);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
ptr = (unsigned long)iref;
|
|
|
|
|
end = (unsigned long)ei + item_size;
|
|
|
|
|
while (ptr < end) {
|
|
|
|
|
iref = (struct btrfs_extent_inline_ref *)ptr;
|
|
|
|
|
type = btrfs_extent_inline_ref_type(eb, iref);
|
|
|
|
|
offset = btrfs_extent_inline_ref_offset(eb, iref);
|
2017-08-18 15:15:24 -06:00
|
|
|
pr_info("\t\tref#%d: ", ref_index++);
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
switch (type) {
|
|
|
|
|
case BTRFS_TREE_BLOCK_REF_KEY:
|
2017-08-18 15:15:24 -06:00
|
|
|
pr_cont("tree block backref root %llu\n", offset);
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_SHARED_BLOCK_REF_KEY:
|
2017-08-18 15:15:24 -06:00
|
|
|
pr_cont("shared block backref parent %llu\n", offset);
|
|
|
|
|
/*
|
|
|
|
|
* offset is supposed to be a tree block which
|
|
|
|
|
* must be aligned to nodesize.
|
|
|
|
|
*/
|
btrfs: require only sector size alignment for parent eb bytenr
commit ea57788eb76dc81f6003245427356a1dcd0ac524 upstream.
[BUG]
A completely sane converted fs will cause kernel warning at balance
time:
[ 1557.188633] BTRFS info (device sda7): relocating block group 8162107392 flags data
[ 1563.358078] BTRFS info (device sda7): found 11722 extents
[ 1563.358277] BTRFS info (device sda7): leaf 7989321728 gen 95 total ptrs 213 free space 3458 owner 2
[ 1563.358280] item 0 key (7984947200 169 0) itemoff 16250 itemsize 33
[ 1563.358281] extent refs 1 gen 90 flags 2
[ 1563.358282] ref#0: tree block backref root 4
[ 1563.358285] item 1 key (7985602560 169 0) itemoff 16217 itemsize 33
[ 1563.358286] extent refs 1 gen 93 flags 258
[ 1563.358287] ref#0: shared block backref parent 7985602560
[ 1563.358288] (parent 7985602560 is NOT ALIGNED to nodesize 16384)
[ 1563.358290] item 2 key (7985635328 169 0) itemoff 16184 itemsize 33
...
[ 1563.358995] BTRFS error (device sda7): eb 7989321728 invalid extent inline ref type 182
[ 1563.358996] ------------[ cut here ]------------
[ 1563.359005] WARNING: CPU: 14 PID: 2930 at 0xffffffff9f231766
Then with transaction abort, and obviously failed to balance the fs.
[CAUSE]
That mentioned inline ref type 182 is completely sane, it's
BTRFS_SHARED_BLOCK_REF_KEY, it's some extra check making kernel to
believe it's invalid.
Commit 64ecdb647ddb ("Btrfs: add one more sanity check for shared ref
type") introduced extra checks for backref type.
One of the requirement is, parent bytenr must be aligned to node size,
which is not correct.
One example is like this:
0 1G 1G+4K 2G 2G+4K
| |///////////////////|//| <- A chunk starts at 1G+4K
| | <- A tree block get reserved at bytenr 1G+4K
Then we have a valid tree block at bytenr 1G+4K, but not aligned to
nodesize (16K).
Such chunk is not ideal, but current kernel can handle it pretty well.
We may warn about such tree block in the future, but should not reject
them.
[FIX]
Change the alignment requirement from node size alignment to sector size
alignment.
Also, to make our lives a little easier, also output @iref when
btrfs_get_extent_inline_ref_type() failed, so we can locate the item
easier.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=205475
Fixes: 64ecdb647ddb ("Btrfs: add one more sanity check for shared ref type")
CC: stable@vger.kernel.org # 4.14+
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Qu Wenruo <wqu@suse.com>
[ update comments and messages ]
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2020-08-26 03:26:43 -06:00
|
|
|
if (!IS_ALIGNED(offset, eb->fs_info->sectorsize))
|
|
|
|
|
pr_info(
|
|
|
|
|
"\t\t\t(parent %llu not aligned to sectorsize %u)\n",
|
|
|
|
|
offset, eb->fs_info->sectorsize);
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_EXTENT_DATA_REF_KEY:
|
|
|
|
|
dref = (struct btrfs_extent_data_ref *)(&iref->offset);
|
|
|
|
|
print_extent_data_ref(eb, dref);
|
|
|
|
|
break;
|
|
|
|
|
case BTRFS_SHARED_DATA_REF_KEY:
|
|
|
|
|
sref = (struct btrfs_shared_data_ref *)(iref + 1);
|
2017-08-18 15:15:24 -06:00
|
|
|
pr_cont("shared data backref parent %llu count %u\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
offset, btrfs_shared_data_ref_count(eb, sref));
|
2017-08-18 15:15:24 -06:00
|
|
|
/*
|
|
|
|
|
* offset is supposed to be a tree block which
|
|
|
|
|
* must be aligned to nodesize.
|
|
|
|
|
*/
|
|
|
|
|
if (!IS_ALIGNED(offset, eb->fs_info->nodesize))
|
btrfs: require only sector size alignment for parent eb bytenr
commit ea57788eb76dc81f6003245427356a1dcd0ac524 upstream.
[BUG]
A completely sane converted fs will cause kernel warning at balance
time:
[ 1557.188633] BTRFS info (device sda7): relocating block group 8162107392 flags data
[ 1563.358078] BTRFS info (device sda7): found 11722 extents
[ 1563.358277] BTRFS info (device sda7): leaf 7989321728 gen 95 total ptrs 213 free space 3458 owner 2
[ 1563.358280] item 0 key (7984947200 169 0) itemoff 16250 itemsize 33
[ 1563.358281] extent refs 1 gen 90 flags 2
[ 1563.358282] ref#0: tree block backref root 4
[ 1563.358285] item 1 key (7985602560 169 0) itemoff 16217 itemsize 33
[ 1563.358286] extent refs 1 gen 93 flags 258
[ 1563.358287] ref#0: shared block backref parent 7985602560
[ 1563.358288] (parent 7985602560 is NOT ALIGNED to nodesize 16384)
[ 1563.358290] item 2 key (7985635328 169 0) itemoff 16184 itemsize 33
...
[ 1563.358995] BTRFS error (device sda7): eb 7989321728 invalid extent inline ref type 182
[ 1563.358996] ------------[ cut here ]------------
[ 1563.359005] WARNING: CPU: 14 PID: 2930 at 0xffffffff9f231766
Then with transaction abort, and obviously failed to balance the fs.
[CAUSE]
That mentioned inline ref type 182 is completely sane, it's
BTRFS_SHARED_BLOCK_REF_KEY, it's some extra check making kernel to
believe it's invalid.
Commit 64ecdb647ddb ("Btrfs: add one more sanity check for shared ref
type") introduced extra checks for backref type.
One of the requirement is, parent bytenr must be aligned to node size,
which is not correct.
One example is like this:
0 1G 1G+4K 2G 2G+4K
| |///////////////////|//| <- A chunk starts at 1G+4K
| | <- A tree block get reserved at bytenr 1G+4K
Then we have a valid tree block at bytenr 1G+4K, but not aligned to
nodesize (16K).
Such chunk is not ideal, but current kernel can handle it pretty well.
We may warn about such tree block in the future, but should not reject
them.
[FIX]
Change the alignment requirement from node size alignment to sector size
alignment.
Also, to make our lives a little easier, also output @iref when
btrfs_get_extent_inline_ref_type() failed, so we can locate the item
easier.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=205475
Fixes: 64ecdb647ddb ("Btrfs: add one more sanity check for shared ref type")
CC: stable@vger.kernel.org # 4.14+
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Qu Wenruo <wqu@suse.com>
[ update comments and messages ]
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2020-08-26 03:26:43 -06:00
|
|
|
pr_info(
|
|
|
|
|
"\t\t\t(parent %llu not aligned to sectorsize %u)\n",
|
|
|
|
|
offset, eb->fs_info->sectorsize);
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
break;
|
|
|
|
|
default:
|
2017-08-18 15:15:24 -06:00
|
|
|
pr_cont("(extent %llu has INVALID ref type %d)\n",
|
2017-08-18 15:15:21 -06:00
|
|
|
eb->start, type);
|
|
|
|
|
return;
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
}
|
|
|
|
|
ptr += btrfs_extent_inline_ref_size(type);
|
|
|
|
|
}
|
|
|
|
|
WARN_ON(ptr > end);
|
|
|
|
|
}
|
|
|
|
|
|
2013-08-15 09:11:18 -06:00
|
|
|
static void print_uuid_item(struct extent_buffer *l, unsigned long offset,
|
|
|
|
|
u32 item_size)
|
|
|
|
|
{
|
|
|
|
|
if (!IS_ALIGNED(item_size, sizeof(u64))) {
|
2013-12-20 09:37:06 -07:00
|
|
|
pr_warn("BTRFS: uuid item with illegal size %lu!\n",
|
2013-08-15 09:11:18 -06:00
|
|
|
(unsigned long)item_size);
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
while (item_size) {
|
|
|
|
|
__le64 subvol_id;
|
|
|
|
|
|
|
|
|
|
read_extent_buffer(l, &subvol_id, offset, sizeof(subvol_id));
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tsubvol_id %llu\n",
|
2013-08-15 09:11:18 -06:00
|
|
|
(unsigned long long)le64_to_cpu(subvol_id));
|
|
|
|
|
item_size -= sizeof(u64);
|
|
|
|
|
offset += sizeof(u64);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2018-04-23 23:03:13 -06:00
|
|
|
/*
|
|
|
|
|
* Helper to output refs and locking status of extent buffer. Useful to debug
|
|
|
|
|
* race condition related problems.
|
|
|
|
|
*/
|
|
|
|
|
static void print_eb_refs_lock(struct extent_buffer *eb)
|
|
|
|
|
{
|
|
|
|
|
#ifdef CONFIG_BTRFS_DEBUG
|
|
|
|
|
btrfs_info(eb->fs_info,
|
|
|
|
|
"refs %u lock (w:%d r:%d bw:%d br:%d sw:%d sr:%d) lock_owner %u current %u",
|
2019-05-02 08:53:47 -06:00
|
|
|
atomic_read(&eb->refs), eb->write_locks,
|
2018-04-23 23:03:13 -06:00
|
|
|
atomic_read(&eb->read_locks),
|
2019-05-02 08:47:23 -06:00
|
|
|
eb->blocking_writers,
|
2018-04-23 23:03:13 -06:00
|
|
|
atomic_read(&eb->blocking_readers),
|
2019-05-02 08:51:53 -06:00
|
|
|
eb->spinning_writers,
|
2018-04-23 23:03:13 -06:00
|
|
|
atomic_read(&eb->spinning_readers),
|
|
|
|
|
eb->lock_owner, current->pid);
|
|
|
|
|
#endif
|
|
|
|
|
}
|
|
|
|
|
|
2017-06-29 10:37:49 -06:00
|
|
|
void btrfs_print_leaf(struct extent_buffer *l)
|
2007-02-24 04:24:44 -07:00
|
|
|
{
|
2017-06-29 10:37:49 -06:00
|
|
|
struct btrfs_fs_info *fs_info;
|
2007-02-24 04:24:44 -07:00
|
|
|
int i;
|
2011-06-23 09:01:01 -06:00
|
|
|
u32 type, nr;
|
2007-03-12 18:12:07 -06:00
|
|
|
struct btrfs_item *item;
|
2007-03-13 14:47:54 -06:00
|
|
|
struct btrfs_root_item *ri;
|
2007-03-15 13:18:43 -06:00
|
|
|
struct btrfs_dir_item *di;
|
2007-03-20 13:57:25 -06:00
|
|
|
struct btrfs_inode_item *ii;
|
2007-04-26 14:46:15 -06:00
|
|
|
struct btrfs_block_group_item *bi;
|
2007-06-18 07:57:58 -06:00
|
|
|
struct btrfs_file_extent_item *fi;
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
struct btrfs_extent_data_ref *dref;
|
|
|
|
|
struct btrfs_shared_data_ref *sref;
|
|
|
|
|
struct btrfs_dev_extent *dev_extent;
|
2007-10-15 14:14:19 -06:00
|
|
|
struct btrfs_key key;
|
|
|
|
|
struct btrfs_key found_key;
|
2007-03-15 13:18:43 -06:00
|
|
|
|
2011-06-23 09:01:01 -06:00
|
|
|
if (!l)
|
|
|
|
|
return;
|
|
|
|
|
|
2017-06-29 10:37:49 -06:00
|
|
|
fs_info = l->fs_info;
|
2011-06-23 09:01:01 -06:00
|
|
|
nr = btrfs_header_nritems(l);
|
|
|
|
|
|
2018-04-11 03:08:12 -06:00
|
|
|
btrfs_info(fs_info,
|
|
|
|
|
"leaf %llu gen %llu total ptrs %d free space %d owner %llu",
|
|
|
|
|
btrfs_header_bytenr(l), btrfs_header_generation(l), nr,
|
2019-03-20 07:36:46 -06:00
|
|
|
btrfs_leaf_free_space(l), btrfs_header_owner(l));
|
2018-04-23 23:03:13 -06:00
|
|
|
print_eb_refs_lock(l);
|
2007-02-24 04:24:44 -07:00
|
|
|
for (i = 0 ; i < nr ; i++) {
|
2013-09-16 08:58:09 -06:00
|
|
|
item = btrfs_item_nr(i);
|
2007-10-15 14:14:19 -06:00
|
|
|
btrfs_item_key_to_cpu(l, &key, i);
|
2014-06-04 10:41:45 -06:00
|
|
|
type = key.type;
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\titem %d key (%llu %u %llu) itemoff %d itemsize %d\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
i, key.objectid, type, key.offset,
|
2007-10-15 14:14:19 -06:00
|
|
|
btrfs_item_offset(l, item), btrfs_item_size(l, item));
|
2007-03-15 10:56:47 -06:00
|
|
|
switch (type) {
|
|
|
|
|
case BTRFS_INODE_ITEM_KEY:
|
2007-03-20 13:57:25 -06:00
|
|
|
ii = btrfs_item_ptr(l, i, struct btrfs_inode_item);
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tinode generation %llu size %llu mode %o\n",
|
2009-01-05 19:25:51 -07:00
|
|
|
btrfs_inode_generation(l, ii),
|
2013-08-20 05:20:07 -06:00
|
|
|
btrfs_inode_size(l, ii),
|
2007-10-15 14:14:19 -06:00
|
|
|
btrfs_inode_mode(l, ii));
|
2007-03-15 10:56:47 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_DIR_ITEM_KEY:
|
2007-03-15 13:18:43 -06:00
|
|
|
di = btrfs_item_ptr(l, i, struct btrfs_dir_item);
|
2007-10-15 14:14:19 -06:00
|
|
|
btrfs_dir_item_key_to_cpu(l, di, &found_key);
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tdir oid %llu type %u\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
found_key.objectid,
|
2007-10-15 14:14:19 -06:00
|
|
|
btrfs_dir_type(l, di));
|
2007-03-15 10:56:47 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_ROOT_ITEM_KEY:
|
|
|
|
|
ri = btrfs_item_ptr(l, i, struct btrfs_root_item);
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\troot data bytenr %llu refs %u\n",
|
2009-01-05 19:25:51 -07:00
|
|
|
btrfs_disk_root_bytenr(l, ri),
|
2007-10-15 14:14:19 -06:00
|
|
|
btrfs_disk_root_refs(l, ri));
|
2007-03-15 10:56:47 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_EXTENT_ITEM_KEY:
|
2014-07-02 11:20:48 -06:00
|
|
|
case BTRFS_METADATA_ITEM_KEY:
|
|
|
|
|
print_extent_item(l, i, type);
|
2007-03-15 10:56:47 -06:00
|
|
|
break;
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
case BTRFS_TREE_BLOCK_REF_KEY:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\ttree block backref\n");
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_SHARED_BLOCK_REF_KEY:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tshared block backref\n");
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_EXTENT_DATA_REF_KEY:
|
|
|
|
|
dref = btrfs_item_ptr(l, i,
|
|
|
|
|
struct btrfs_extent_data_ref);
|
|
|
|
|
print_extent_data_ref(l, dref);
|
|
|
|
|
break;
|
|
|
|
|
case BTRFS_SHARED_DATA_REF_KEY:
|
|
|
|
|
sref = btrfs_item_ptr(l, i,
|
|
|
|
|
struct btrfs_shared_data_ref);
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tshared data backref count %u\n",
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
btrfs_shared_data_ref_count(l, sref));
|
2007-12-11 07:25:06 -07:00
|
|
|
break;
|
2007-06-18 07:57:58 -06:00
|
|
|
case BTRFS_EXTENT_DATA_KEY:
|
|
|
|
|
fi = btrfs_item_ptr(l, i,
|
|
|
|
|
struct btrfs_file_extent_item);
|
2007-10-15 14:14:19 -06:00
|
|
|
if (btrfs_file_extent_type(l, fi) ==
|
2007-06-18 07:57:58 -06:00
|
|
|
BTRFS_FILE_EXTENT_INLINE) {
|
2018-06-06 01:41:49 -06:00
|
|
|
pr_info("\t\tinline extent data size %llu\n",
|
|
|
|
|
btrfs_file_extent_ram_bytes(l, fi));
|
2007-06-18 07:57:58 -06:00
|
|
|
break;
|
|
|
|
|
}
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\textent data disk bytenr %llu nr %llu\n",
|
2009-01-05 19:25:51 -07:00
|
|
|
btrfs_file_extent_disk_bytenr(l, fi),
|
|
|
|
|
btrfs_file_extent_disk_num_bytes(l, fi));
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\textent data offset %llu nr %llu ram %llu\n",
|
2009-01-05 19:25:51 -07:00
|
|
|
btrfs_file_extent_offset(l, fi),
|
|
|
|
|
btrfs_file_extent_num_bytes(l, fi),
|
|
|
|
|
btrfs_file_extent_ram_bytes(l, fi));
|
2007-06-18 07:57:58 -06:00
|
|
|
break;
|
Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE)
This commit introduces a new kind of back reference for btrfs metadata.
Once a filesystem has been mounted with this commit, IT WILL NO LONGER
BE MOUNTABLE BY OLDER KERNELS.
When a tree block in subvolume tree is cow'd, the reference counts of all
extents it points to are increased by one. At transaction commit time,
the old root of the subvolume is recorded in a "dead root" data structure,
and the btree it points to is later walked, dropping reference counts
and freeing any blocks where the reference count goes to 0.
The increments done during cow and decrements done after commit cancel out,
and the walk is a very expensive way to go about freeing the blocks that
are no longer referenced by the new btree root. This commit reduces the
transaction overhead by avoiding the need for dead root records.
When a non-shared tree block is cow'd, we free the old block at once, and the
new block inherits old block's references. When a tree block with reference
count > 1 is cow'd, we increase the reference counts of all extents
the new block points to by one, and decrease the old block's reference count by
one.
This dead tree avoidance code removes the need to modify the reference
counts of lower level extents when a non-shared tree block is cow'd.
But we still need to update back ref for all pointers in the block.
This is because the location of the block is recorded in the back ref
item.
We can solve this by introducing a new type of back ref. The new
back ref provides information about pointer's key, level and in which
tree the pointer lives. This information allow us to find the pointer
by searching the tree. The shortcoming of the new back ref is that it
only works for pointers in tree blocks referenced by their owner trees.
This is mostly a problem for snapshots, where resolving one of these
fuzzy back references would be O(number_of_snapshots) and quite slow.
The solution used here is to use the fuzzy back references in the common
case where a given tree block is only referenced by one root,
and use the full back references when multiple roots have a reference
on a given block.
This commit adds per subvolume red-black tree to keep trace of cached
inodes. The red-black tree helps the balancing code to find cached
inodes whose inode numbers within a given range.
This commit improves the balancing code by introducing several data
structures to keep the state of balancing. The most important one
is the back ref cache. It caches how the upper level tree blocks are
referenced. This greatly reduce the overhead of checking back ref.
The improved balancing code scales significantly better with a large
number of snapshots.
This is a very large commit and was written in a number of
pieces. But, they depend heavily on the disk format change and were
squashed together to make sure git bisect didn't end up in a
bad state wrt space balancing or the format change.
Signed-off-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 08:45:14 -06:00
|
|
|
case BTRFS_EXTENT_REF_V0_KEY:
|
2018-06-26 07:57:36 -06:00
|
|
|
btrfs_print_v0_err(fs_info);
|
|
|
|
|
btrfs_handle_fs_error(fs_info, -EINVAL, NULL);
|
2011-01-25 23:22:33 -07:00
|
|
|
break;
|
2007-04-26 14:46:15 -06:00
|
|
|
case BTRFS_BLOCK_GROUP_ITEM_KEY:
|
|
|
|
|
bi = btrfs_item_ptr(l, i,
|
|
|
|
|
struct btrfs_block_group_item);
|
2017-05-25 18:08:12 -06:00
|
|
|
pr_info(
|
|
|
|
|
"\t\tblock group used %llu chunk_objectid %llu flags %llu\n",
|
|
|
|
|
btrfs_disk_block_group_used(l, bi),
|
|
|
|
|
btrfs_disk_block_group_chunk_objectid(l, bi),
|
|
|
|
|
btrfs_disk_block_group_flags(l, bi));
|
2007-03-15 10:56:47 -06:00
|
|
|
break;
|
2008-03-24 13:01:56 -06:00
|
|
|
case BTRFS_CHUNK_ITEM_KEY:
|
2009-01-05 19:25:51 -07:00
|
|
|
print_chunk(l, btrfs_item_ptr(l, i,
|
|
|
|
|
struct btrfs_chunk));
|
2008-03-24 13:01:56 -06:00
|
|
|
break;
|
|
|
|
|
case BTRFS_DEV_ITEM_KEY:
|
|
|
|
|
print_dev_item(l, btrfs_item_ptr(l, i,
|
|
|
|
|
struct btrfs_dev_item));
|
|
|
|
|
break;
|
|
|
|
|
case BTRFS_DEV_EXTENT_KEY:
|
|
|
|
|
dev_extent = btrfs_item_ptr(l, i,
|
|
|
|
|
struct btrfs_dev_extent);
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tdev extent chunk_tree %llu\n\t\tchunk objectid %llu chunk offset %llu length %llu\n",
|
2008-04-15 13:41:47 -06:00
|
|
|
btrfs_dev_extent_chunk_tree(l, dev_extent),
|
|
|
|
|
btrfs_dev_extent_chunk_objectid(l, dev_extent),
|
|
|
|
|
btrfs_dev_extent_chunk_offset(l, dev_extent),
|
|
|
|
|
btrfs_dev_extent_length(l, dev_extent));
|
2013-01-30 17:54:57 -07:00
|
|
|
break;
|
2016-01-25 10:44:13 -07:00
|
|
|
case BTRFS_PERSISTENT_ITEM_KEY:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tpersistent item objectid %llu offset %llu\n",
|
2016-01-25 10:44:13 -07:00
|
|
|
key.objectid, key.offset);
|
|
|
|
|
switch (key.objectid) {
|
|
|
|
|
case BTRFS_DEV_STATS_OBJECTID:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tdevice stats\n");
|
2016-01-25 10:44:13 -07:00
|
|
|
break;
|
|
|
|
|
default:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tunknown persistent item\n");
|
2016-01-25 10:44:13 -07:00
|
|
|
}
|
2012-05-25 08:06:10 -06:00
|
|
|
break;
|
2016-01-25 10:44:13 -07:00
|
|
|
case BTRFS_TEMPORARY_ITEM_KEY:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\ttemporary item objectid %llu offset %llu\n",
|
2016-01-25 10:44:13 -07:00
|
|
|
key.objectid, key.offset);
|
|
|
|
|
switch (key.objectid) {
|
|
|
|
|
case BTRFS_BALANCE_OBJECTID:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tbalance status\n");
|
2016-01-25 10:44:13 -07:00
|
|
|
break;
|
|
|
|
|
default:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tunknown temporary item\n");
|
2016-01-25 10:44:13 -07:00
|
|
|
}
|
|
|
|
|
break;
|
2012-11-05 09:32:20 -07:00
|
|
|
case BTRFS_DEV_REPLACE_KEY:
|
2016-09-20 08:05:01 -06:00
|
|
|
pr_info("\t\tdev replace\n");
|
2012-11-05 09:32:20 -07:00
|
|
|
break;
|
2013-08-15 09:11:18 -06:00
|
|
|
case BTRFS_UUID_KEY_SUBVOL:
|
|
|
|
|
case BTRFS_UUID_KEY_RECEIVED_SUBVOL:
|
|
|
|
|
print_uuid_item(l, btrfs_item_ptr_offset(l, i),
|
|
|
|
|
btrfs_item_size_nr(l, i));
|
|
|
|
|
break;
|
2007-03-15 10:56:47 -06:00
|
|
|
};
|
2007-02-24 04:24:44 -07:00
|
|
|
}
|
|
|
|
|
}
|
2007-03-22 10:13:20 -06:00
|
|
|
|
2018-04-11 03:08:12 -06:00
|
|
|
void btrfs_print_tree(struct extent_buffer *c, bool follow)
|
2007-02-24 04:24:44 -07:00
|
|
|
{
|
2017-06-29 10:37:49 -06:00
|
|
|
struct btrfs_fs_info *fs_info;
|
2008-04-15 13:41:47 -06:00
|
|
|
int i; u32 nr;
|
2007-10-15 14:14:19 -06:00
|
|
|
struct btrfs_key key;
|
2007-10-15 14:15:53 -06:00
|
|
|
int level;
|
2007-02-24 04:24:44 -07:00
|
|
|
|
2007-10-15 14:14:19 -06:00
|
|
|
if (!c)
|
2007-02-24 04:24:44 -07:00
|
|
|
return;
|
2017-06-29 10:37:49 -06:00
|
|
|
fs_info = c->fs_info;
|
2007-10-15 14:14:19 -06:00
|
|
|
nr = btrfs_header_nritems(c);
|
2007-10-15 14:15:53 -06:00
|
|
|
level = btrfs_header_level(c);
|
|
|
|
|
if (level == 0) {
|
2017-06-29 10:37:49 -06:00
|
|
|
btrfs_print_leaf(c);
|
2007-02-24 04:24:44 -07:00
|
|
|
return;
|
|
|
|
|
}
|
2016-06-22 16:54:23 -06:00
|
|
|
btrfs_info(fs_info,
|
2018-04-11 03:08:12 -06:00
|
|
|
"node %llu level %d gen %llu total ptrs %d free spc %u owner %llu",
|
|
|
|
|
btrfs_header_bytenr(c), level, btrfs_header_generation(c),
|
|
|
|
|
nr, (u32)BTRFS_NODEPTRS_PER_BLOCK(fs_info) - nr,
|
|
|
|
|
btrfs_header_owner(c));
|
2018-04-23 23:03:13 -06:00
|
|
|
print_eb_refs_lock(c);
|
2007-02-24 04:24:44 -07:00
|
|
|
for (i = 0; i < nr; i++) {
|
2007-10-15 14:14:19 -06:00
|
|
|
btrfs_node_key_to_cpu(c, &key, i);
|
2018-04-11 03:08:12 -06:00
|
|
|
pr_info("\tkey %d (%llu %u %llu) block %llu gen %llu\n",
|
2013-08-20 05:20:07 -06:00
|
|
|
i, key.objectid, key.type, key.offset,
|
2018-04-11 03:08:12 -06:00
|
|
|
btrfs_node_blockptr(c, i),
|
|
|
|
|
btrfs_node_ptr_generation(c, i));
|
2007-02-24 04:24:44 -07:00
|
|
|
}
|
2018-04-11 03:08:12 -06:00
|
|
|
if (!follow)
|
|
|
|
|
return;
|
2007-02-24 04:24:44 -07:00
|
|
|
for (i = 0; i < nr; i++) {
|
2018-03-28 19:08:11 -06:00
|
|
|
struct btrfs_key first_key;
|
|
|
|
|
struct extent_buffer *next;
|
|
|
|
|
|
|
|
|
|
btrfs_node_key_to_cpu(c, &first_key, i);
|
|
|
|
|
next = read_tree_block(fs_info, btrfs_node_blockptr(c, i),
|
|
|
|
|
btrfs_node_ptr_generation(c, i),
|
|
|
|
|
level - 1, &first_key);
|
2016-09-14 18:23:39 -06:00
|
|
|
if (IS_ERR(next)) {
|
|
|
|
|
continue;
|
|
|
|
|
} else if (!extent_buffer_uptodate(next)) {
|
|
|
|
|
free_extent_buffer(next);
|
|
|
|
|
continue;
|
|
|
|
|
}
|
|
|
|
|
|
2007-03-12 10:01:18 -06:00
|
|
|
if (btrfs_is_leaf(next) &&
|
2009-07-22 14:52:13 -06:00
|
|
|
level != 1)
|
2007-02-24 04:24:44 -07:00
|
|
|
BUG();
|
2007-10-15 14:14:19 -06:00
|
|
|
if (btrfs_header_level(next) !=
|
2009-07-22 14:52:13 -06:00
|
|
|
level - 1)
|
2007-02-24 04:24:44 -07:00
|
|
|
BUG();
|
2018-04-11 03:08:12 -06:00
|
|
|
btrfs_print_tree(next, follow);
|
2007-10-15 14:14:19 -06:00
|
|
|
free_extent_buffer(next);
|
2007-02-24 04:24:44 -07:00
|
|
|
}
|
|
|
|
|
}
|