diff options
author | 2014-12-19 18:38:47 +0100 | |
---|---|---|
committer | 2015-01-21 18:02:03 -0800 | |
commit | 5efa0490cc94aee06cd8d282683e22a8ce0a0026 (patch) | |
tree | 2122a35a055b1340eaae6776c6ad86c43f2369a1 | |
parent | btrfs: update message levels after checksum errors (diff) | |
download | wireguard-linux-5efa0490cc94aee06cd8d282683e22a8ce0a0026.tar.xz wireguard-linux-5efa0490cc94aee06cd8d282683e22a8ce0a0026.zip |
btrfs: set proper message level for skinny metadata
This has been confusing people for too long, the message is really just
informative.
CC: <stable@vger.kernel.org> # 3.10+
Signed-off-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to '')
-rw-r--r-- | fs/btrfs/disk-io.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c index 20da68206fba..0696a103751e 100644 --- a/fs/btrfs/disk-io.c +++ b/fs/btrfs/disk-io.c @@ -2509,7 +2509,7 @@ int open_ctree(struct super_block *sb, features |= BTRFS_FEATURE_INCOMPAT_COMPRESS_LZO; if (features & BTRFS_FEATURE_INCOMPAT_SKINNY_METADATA) - printk(KERN_ERR "BTRFS: has skinny extents\n"); + printk(KERN_INFO "BTRFS: has skinny extents\n"); /* * flag our filesystem as having big metadata blocks if |