[Bugs] [Bug 1231224] New: Misleading error messages on brick logs while creating directory (mkdir) on fuse mount

bugzilla at redhat.com bugzilla at redhat.com
Fri Jun 12 12:42:23 UTC 2015


            Bug ID: 1231224
           Summary: Misleading error messages on brick logs while creating
                    directory (mkdir) on fuse mount
           Product: GlusterFS
           Version: mainline
         Component: locks
          Assignee: bugs at gluster.org
          Reporter: aspandey at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com

Description of problem:
Error messages are getting logged on brick logs while creating directories on
fuse mount for disperse volumes.

Version-Release number of selected component (if applicable):

[root at aspandey gfsa]# gluster --version
glusterfs 3.8dev built on Jun 12 2015 18:03:10
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.

How reproducible:

Steps to Reproduce:
1. Create disperse volume 1 x (4+2)
2. mount as glusterfs on a mount point /mnt
3. create a directory on mount point i.e. /mnt

See the brick logs. Following error messages are present -

[2015-06-12 12:35:14.351684] I [MSGID: 115029]
[server-handshake.c:588:server_setvolume] 0-gfs-server: accepted client from
aspandey-8997-2015/06/12-12:35:14:330840-gfs-client-0-0-0 (version: 3.8dev)
[2015-06-12 12:35:23.789708] E [posix-helpers.c:1087:posix_handle_pair]
0-gfs-posix: /brick/gluster/rep/A1/dir: key:glusterfs.inodelk-dom-count flags:
1 length:15 error:Operation not supported
[2015-06-12 12:35:23.789731] E [posix.c:1386:posix_mkdir] 0-gfs-posix: setting
xattrs on /brick/gluster/rep/A1/dir failed (Operation not supported)

Actual results:
Misleading error messages in brick logs.

Expected results:
There should not be any error message for successful fop's for example
directory creation (mkdir).

Additional info:

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