Bug 811957 - running dbench in loop reports "Extended attributes not supported" in brick logs
Summary: running dbench in loop reports "Extended attributes not supported" in brick logs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-04-12 11:48 UTC by Shwetha Panduranga
Modified: 2013-12-19 00:07 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:37:34 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Brick Log (15.55 MB, text/x-log)
2012-04-12 11:48 UTC, Shwetha Panduranga
no flags Details

Description Shwetha Panduranga 2012-04-12 11:48:04 UTC
Created attachment 577046 [details]
Brick Log

Description of problem:

The brick log should ideally notify what is the "key extended attribute" for which operation is not supported. 

Note:- No dbench application failure. 

[2012-04-12 22:06:23.195883] W [posix-helpers.c:663:posix_handle_pair] 0-dstore-posix: Extended attributes not supported
[2012-04-12 22:06:23.195961] I [server3_1-fops.c:897:server_setxattr_cbk] 0-dstore-server: 1211074: SETXATTR /clients/client0/~dmtmp/PARADOX/STUDENTS.TV (fa00b5e3-77d6-4a10-a9bf-6cefdfcb7773) ==> -1 (Operation not supported)
[2012-04-12 22:06:23.210999] I [server3_1-fops.c:897:server_setxattr_cbk] 0-dstore-server: 1211090: SETXATTR /clients/client8/~dmtmp/PARADOX/STUDENTS.PX (de3cb6e6-5017-4870-8c94-6d5643947ae1) ==> -1 (Operation not supported)
[2012-04-12 22:06:23.223347] I [server3_1-fops.c:897:server_setxattr_cbk] 0-dstore-server: 1211101: SETXATTR /clients/client4/~dmtmp/PARADOX/COURSES.DB (15174f28-be10-466b-abba-d315962eb6c2) ==> -1 (Operation not supported)
[2012-04-12 22:06:23.225733] I [server3_1-fops.c:818:server_getxattr_cbk] 0-dstore-server: 1211105: GETXATTR /clients/client9/~dmtmp/PARADOX/COURSES.DB (user.DosAttrib) ==> -1 (Operation not supported)
[2012-04-12 22:06:23.237674] I [server3_1-fops.c:818:server_getxattr_cbk] 0-dstore-server: 1211113: GETXATTR /clients/client8/~dmtmp/PARADOX/STUDENTS.XG0 (user.DosAttrib) ==> -1 (Operation not supported)
[2012-04-12 22:06:23.248844] I [server3_1-fops.c:818:server_getxattr_cbk] 0-dstore-server: 1211121: GETXATTR /clients/client9/~dmtmp/PARADOX/COURSES.DB (user.DosAttrib) ==> -1 (Operation not supported)


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

How reproducible:
often

run_dbench.sh:-
--------------
#!/bin/bash

while true;
	do
	dbench -s -F -S --stat-check 10
	dbench -s -F -S -x --one-byte-write-fix --stat-check 10
	done


Steps to Reproduce:
1.create a replicate volume (1x3).start the volume
2.create a fuse mount.
3.on the fuse mount execute "run_dbench.sh"
  
Actual results:
The brick log repeatedly reports Setxattr, Getxattr operation not supported

Additional Info:-
-----------------
[04/12/12 - 21:59:54 root@APP-SERVER1 ~]# gluster volume info
 
Volume Name: dstore
Type: Replicate
Volume ID: bfddf295-51a2-48ab-b048-cd7dcfa3f91e
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 192.168.2.35:/export1/dstore1
Brick2: 192.168.2.36:/export1/dstore1
Brick3: 192.168.2.37:/export1/dstore1



[04/12/12 - 22:10:19 root@APP-SERVER1 ~]# setfattr -n user.testing /export1/dstore1/iozone.tmp 
setfattr: /export1/dstore1/iozone.tmp: Operation not supported
[04/12/12 - 22:10:40 root@APP-SERVER1 ~]# mount -o remount,user_xattr /export1
[04/12/12 - 22:11:07 root@APP-SERVER1 ~]# setfattr -n user.testing /export1/dstore1/iozone.tmp 



[04/12/12 - 22:12:23 root@APP-SERVER1 ~]# gluster volume status dstore detail

Status of volume: dstore
------------------------------------------------------------------------------
Brick                : Brick 192.168.2.35:/export1/dstore1
Port                 : 24009               
Online               : Y                   
Pid                  : 30484               
File System          : ext4                
Device               : /dev/sdb1           
Mount Options        : rw,user_xattr       
Inode Size           : 256                 
Disk Space Free      : 96.2GB              
Total Disk Space     : 98.4GB              
Inode Count          : 6553600             
Free Inodes          : 6486744             
------------------------------------------------------------------------------
Brick                : Brick 192.168.2.36:/export1/dstore1
Port                 : 24009               
Online               : Y                   
Pid                  : 19627               
File System          : xfs                 
Device               : /dev/sdb1           
Mount Options        : rw                  
Inode Size           : 256                 
Disk Space Free      : 98.1GB              
Total Disk Space     : 99.9GB              
Inode Count          : 104856192           
Free Inodes          : 104789358           
------------------------------------------------------------------------------
Brick                : Brick 192.168.2.37:/export1/dstore1
Port                 : 24009               
Online               : Y                   
Pid                  : 15774               
File System          : xfs                 
Device               : /dev/sdb1           
Mount Options        : rw                  
Inode Size           : 256                 
Disk Space Free      : 97.5GB              
Total Disk Space     : 99.9GB              
Inode Count          : 104856192           
Free Inodes          : 104789358

Comment 1 Amar Tumballi 2012-04-13 02:17:52 UTC
the issue came up because the 'user_xattr' flag was not present on the backend mount. But bug here is that log messages are not complete to debug the issues.

Comment 2 Amar Tumballi 2012-04-23 11:25:47 UTC
patch sent @ http://review.gluster.com/3140

Comment 3 Anand Avati 2012-05-03 06:01:15 UTC
CHANGE: http://review.gluster.com/3140 (log cleanup: in setxattr() path) merged in master by Vijay Bellur (vijay)

Comment 4 Shwetha Panduranga 2012-05-04 08:16:26 UTC
Bug is fixed . verified on 3.3.0qa39


Note You need to log in before you can comment on or make changes to this bug.