Matthew Dillon wrote:
Don't bother trying to rebalance. It won't actually hurt the filesystem
much to not rebalance. The rebalancer needs a lot of buffer cache
buffers to operate at the moment and there's no easy solution other
then to add memory.
-Matt
Matt,
I get this with even 512MB of ram, as it does not seem to be something
we need people to worry about can we subdue the message unless
vfs.hammer.debug.general is 0x0080??
0x0080 might not been the correct one to use, but seemed to be popular,
is there a list of reasons for each one used in debug_general?
Attached is a patch.
Thanks,
Dylan
From 52862807299d79f0253d428a0b1529ad63e87bf3 Mon Sep 17 00:00:00 2001
From: Dylan Reinhold dy...@ocnetworking.com
Date: Tue, 27 Apr 2010 22:04:21 -0700
Subject: [PATCH] HAMMER: Suppress rebalance buffer message.
Only show the message if debug.general is 0x0080
---
sys/vfs/hammer/hammer_ioctl.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/sys/vfs/hammer/hammer_ioctl.c b/sys/vfs/hammer/hammer_ioctl.c
index f8fe994..dc7eb90 100644
--- a/sys/vfs/hammer/hammer_ioctl.c
+++ b/sys/vfs/hammer/hammer_ioctl.c
@@ -94,9 +94,11 @@ hammer_ioctl(hammer_inode_t ip, u_long com, caddr_t data, int fflag,
* little memory will not be able to do it.
*/
if (error == 0 nbuf HAMMER_REBALANCE_MIN_BUFS) {
- kprintf(hammer: System has insufficient buffers
-to rebalance the tree. nbuf %d\n,
+ if (hammer_debug_general 0x0080) {
+kprintf(hammer: System has insufficient
+buffers to rebalance the tree. nbuf %d\n,
HAMMER_REBALANCE_MIN_BUFS);
+ }
error = ENOSPC;
}
if (error == 0) {
--
1.6.4