[Bugs] [Bug 1202758] New: Disperse volume: brick logs are getting filled with "anonymous fd creation failed" messages
bugzilla at redhat.com
bugzilla at redhat.com
Tue Mar 17 12:07:47 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1202758
Bug ID: 1202758
Summary: Disperse volume: brick logs are getting filled with
"anonymous fd creation failed" messages
Product: GlusterFS
Version: mainline
Component: disperse
Assignee: bugs at gluster.org
Reporter: byarlaga at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Created attachment 1002781
--> https://bugzilla.redhat.com/attachment.cgi?id=1002781&action=edit
sosreport of client
Description of problem:
=======================
Brick logs are getting filled with below messages and the filesystem is full
within no time.
[2015-03-17 11:56:04.171990] W [server-resolve.c:425:resolve_anonfd_simple]
0-server: inode for the gfid (ea84b493-b049-487a-825b-cb4bece296d7) is not
found. anonymous fd creation failed
[2015-03-17 11:56:04.172063] W [server-resolve.c:425:resolve_anonfd_simple]
0-server: inode for the gfid (ea84b493-b049-487a-825b-cb4bece296d7) is not
found. anonymous fd creation failed
[2015-03-17 11:56:04.172489] W [server-resolve.c:425:resolve_anonfd_simple]
0-server: inode for the gfid (b8bb35ff-1641-49c8-8ce2-b07f35fd4ef7) is not
found. anonymous fd creation failed
[2015-03-17 11:56:04.172567] W [server-resolve.c:425:resolve_anonfd_simple]
0-server: inode for the gfid (b8bb35ff-1641-49c8-8ce2-b07f35fd4ef7) is not
found. anonymous fd creation failed
Version-Release number of selected component (if applicable):
=============================================================
[root at vertigo tmp]# gluster --version
glusterfs 3.7dev built on Mar 12 2015 01:40:59
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.
[root at vertigo tmp]#
How reproducible:
=================
Tried once
Steps to Reproduce:
1. Create a 1x(8+4) disperse volume and nfs/fuse mount on the client
2. Untar linux kernel images in parallel of about 20 instances
3. Bring down 4 bricks for some time and bring them back up with "gluster
volume start force"
4. Trigger full heal from server
5. On the client do a 'du -sh ." on the untarred directory. (Not sure if this
has to do anything with log getting filled up)
Actual results:
Expected results:
Additional info:
================
sosreports of server and clients will be attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list