summaryrefslogtreecommitdiff
path: root/ctree.h
diff options
context:
space:
mode:
authorRobin Dong <sanbai@taobao.com>2012-09-27 21:02:39 -0600
committerroot <root@localhost.localdomain>2012-10-04 16:26:34 -0400
commit32be2a1164b58b37af7c38e83bb2d30b1095e224 (patch)
tree026c628ab222130487f4d3957fc9a09aa37466c6 /ctree.h
parent29db8b12cd06e7eb2e6789ad896c40837db610e5 (diff)
btrfs-progs: limit the max value of leafsize and nodesize
Using mkfs.btrfs like: mkfs.btrfs -l 131072 /dev/sda will return no error, but after mount it, the dmesg will report: BTRFS: couldn't mount because metadata blocksize (131072) was too large The leafsize and nodesize are equal at present, so we just use one function "check_leaf_or_node_size" to limit leaf and node size below BTRFS_MAX_METADATA_BLOCKSIZE. Signed-off-by: Robin Dong <sanbai@taobao.com> Reviewed-by: David Sterba <dave@jikos.cz> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'ctree.h')
-rw-r--r--ctree.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/ctree.h b/ctree.h
index 4bb66fff..293b24fe 100644
--- a/ctree.h
+++ b/ctree.h
@@ -111,6 +111,12 @@ struct btrfs_trans_handle;
#define BTRFS_DEV_ITEMS_OBJECTID 1ULL
/*
+ * the max metadata block size. This limit is somewhat artificial,
+ * but the memmove costs go through the roof for larger blocks.
+ */
+#define BTRFS_MAX_METADATA_BLOCKSIZE 65536
+
+/*
* we can actually store much bigger names, but lets not confuse the rest
* of linux
*/