Hi, These messages (no element to prune) are just debug messages, no need to be worried about them. In the stable code base, we will remove all these confusing/unneccessary debug log messages. Till then you may expect your log file to grow *very* large with -LDEBUG flag. -amar On 7/11/07, Pooya Woodcock <pooya@xxxxxxxxxxxxxxx> wrote:
Hi everyone, been a while since I last posted since I've been running very table in the 2.4 branch. Just recently I took the plunge--- I am running mainline 2.5 latest TLA as for an hour ago (294?) 2007-07-10 12:01:11 D [inode.c:332:__passive_inode] brick-afr/inode: passivating inode(34735742), lru=56/1000 2007-07-10 12:01:11 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:01:11 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:01:11 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:01:11 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:01:11 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:01:12 D [inode.c:302:__active_inode] brick-afr/inode: activating inode(34685086), lru=55/1000 2007-07-10 12:01:12 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:01:12 D [inode.c:332:__passive_inode] brick-afr/inode: passivating inode(34685086), lru=56/1000 2007-07-10 12:01:12 D [inode.c:302:__active_inode] brick/inode: activating inode(11862174), lru=55/1000 2007-07-10 12:01:12 D [server-protocol.c:639:server_inode_prune] locks: no element to prune 2007-07-10 12:01:12 D [inode.c:332:__passive_inode] brick/inode: passivating inode(11862174), lru=56/1000 2007-07-10 12:01:12 D [inode.c:302:__active_inode] brick/inode: activating inode(11912029), lru=55/1000 There are lots of "no element to prune"s on my daemon log files. Should I worry about this? [root@node04 ~]# tail /var/log/glusterfsd.log 2007-07-10 12:03:45 D [inode.c:332:__passive_inode] brick-afr/inode: passivating inode(10552395), lru=57/1000 2007-07-10 12:03:45 D [inode.c:302:__active_inode] brick-afr/inode: activating inode(10552395), lru=56/1000 2007-07-10 12:03:45 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:03:45 D [inode.c:302:__active_inode] brick-afr/inode: activating inode(10552520), lru=55/1000 2007-07-10 12:03:45 D [server-protocol.c:639:server_inode_prune] locks-afr: no element to prune 2007-07-10 12:03:45 D [inode.c:332:__passive_inode] brick-afr/inode: passivating inode(10552520), lru=56/1000 2007-07-10 12:03:45 D [inode.c:302:__active_inode] brick/inode: activating inode(12141234), lru=56/1000 2007-07-10 12:03:45 D [server-protocol.c:639:server_inode_prune] locks: no element to prune 2007-07-10 12:03:45 D [inode.c:332:__passive_inode] brick/inode: passivating inode(12141234), lru=57/1000 2007-07-10 12:03:45 D [server-protocol.c:639:server_inode_prune] locks: no element to prune _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/gluster-devel
-- Amar Tumballi http://amar.80x25.org [bulde on #gluster/irc.gnu.org]
