From: Josef Bacik <jbacik@fb.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH] Btrfs-progs: make free space cache less noisy
Date: Wed, 1 Oct 2014 10:11:09 -0400 [thread overview]
Message-ID: <1412172669-1975-1-git-send-email-jbacik@fb.com> (raw)
Fsck only cares if the cache is really broken, so don't be noisy if the
generations don't match or other such errors. Thanks,
Signed-off-by: Josef Bacik <jbacik@fb.com>
---
free-space-cache.c | 14 +-------------
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/free-space-cache.c b/free-space-cache.c
index 2440dd8..43c0894 100644
--- a/free-space-cache.c
+++ b/free-space-cache.c
@@ -174,9 +174,6 @@ static int io_ctl_check_generation(struct io_ctl *io_ctl, u64 generation)
gen = io_ctl->cur;
if (le64_to_cpu(*gen) != generation) {
- printk("btrfs: space cache generation "
- "(%Lu) does not match inode (%Lu)\n", *gen,
- generation);
io_ctl_unmap_page(io_ctl);
return -EIO;
}
@@ -318,11 +315,6 @@ static int __load_free_space_cache(struct btrfs_root *root,
}
if (btrfs_inode_generation(leaf, inode_item) != generation) {
- printf("free space inode generation (%llu) did not match "
- "free space cache generation (%llu)\n",
- (unsigned long long)btrfs_inode_generation(leaf,
- inode_item),
- (unsigned long long)generation);
btrfs_release_path(path);
return 0;
}
@@ -434,13 +426,9 @@ int load_free_space_cache(struct btrfs_fs_info *fs_info,
block_group->key.objectid);
btrfs_free_path(path);
- if (ret < 0) {
+ if (ret < 0)
ret = 0;
- printf("failed to load free space cache for block group %llu\n",
- block_group->key.objectid);
- }
-
return ret;
}
--
1.8.3.1
next reply other threads:[~2014-10-01 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 14:11 Josef Bacik [this message]
2014-10-06 16:42 ` [PATCH] Btrfs-progs: make free space cache less noisy David Sterba
2014-10-06 17:08 ` David Sterba
2014-10-06 16:48 ` [PATCH] btrfs-progs: check, add verbosity level option 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=1412172669-1975-1-git-send-email-jbacik@fb.com \
--to=jbacik@fb.com \
--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).