Description of problem:
while creating data I found the issue, that for some the brick logs were reporting "E" msgs.
even though the same files are created


Volume Name: dist-rep3
Type: Distributed-Replicate
Volume ID: 75ce853a-fa9c-442e-9705-4408535ab9be
Status: Started
Number of Bricks: 6 x 2 = 12
Transport-type: tcp
Bricks:
Brick1: 10.70.42.186:/rhs/brick1/d1r13
Brick2: 10.70.43.181:/rhs/brick1/d1r23
Brick3: 10.70.43.18:/rhs/brick1/d2r13
Brick4: 10.70.43.22:/rhs/brick1/d2r23
Brick5: 10.70.42.186:/rhs/brick1/d3r13
Brick6: 10.70.43.181:/rhs/brick1/d3r23
Brick7: 10.70.43.18:/rhs/brick1/d4r13
Brick8: 10.70.43.22:/rhs/brick1/d4r23
Brick9: 10.70.42.186:/rhs/brick1/d5r13
Brick10: 10.70.43.181:/rhs/brick1/d5r23
Brick11: 10.70.43.18:/rhs/brick1/d6r13
Brick12: 10.70.43.22:/rhs/brick1/d6r23
Options Reconfigured:
features.quota: on

[root@quota1 ~]# gluster volume quota dist-rep3 list
                  Path                   Hard-limit Soft-limit   Used  Available
--------------------------------------------------------------------------------
/                                          2.0GB       80%       2.0GB  0Bytes


Version-Release number of selected component (if applicable):
glusterfs-3.4.0.34rhs-1.el6rhs.x86_64

How reproducible:
happen to be seen this

Steps to Reproduce:
1. had a quota set for 1GB on "/"
2. increased it to 2GB "/"
3. over nfs mount started creating data.

Actual results:
from brick logs,

[2013-10-11 18:25:29.256722] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.84 failed (Operation not supported)
[2013-10-11 18:25:31.172168] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.85 failed (Operation not supported)
[2013-10-11 18:25:33.086564] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.86 failed (Operation not supported)
[2013-10-11 18:25:35.003860] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.87 failed (Operation not supported)
[2013-10-11 18:25:36.891386] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.88 failed (Operation not supported)
[2013-10-11 18:25:38.947450] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.89 failed (Operation not supported)
[2013-10-11 18:25:41.107094] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.90 failed (Operation not supported)
[2013-10-11 18:25:42.994648] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.91 failed (Operation not supported)
[2013-10-11 18:25:44.965115] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.92 failed (Operation not supported)
[2013-10-11 18:25:46.892014] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.93 failed (Operation not supported)
[2013-10-11 18:25:48.865419] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.94 failed (Operation not supported)
[2013-10-11 18:25:50.775208] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.95 failed (Operation not supported)
[2013-10-11 18:25:52.806413] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.96 failed (Operation not supported)
[2013-10-11 18:25:54.795349] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.97 failed (Operation not supported)
[2013-10-11 18:25:56.855082] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.98 failed (Operation not supported)
[2013-10-11 18:25:58.860923] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.99 failed (Operation not supported)
[2013-10-11 18:26:00.750788] E [posix.c:1933:posix_create] 0-dist-rep3-posix: setting xattrs on /rhs/brick1/d1r13/dir/f.100 failed (Operation not supported)


pointing out xattrs of f.100,
[root@quota1 ~]# getfattr -m . -d -e hex /rhs/brick1/d1r13/dir/f.100
getfattr: Removing leading '/' from absolute path names
# file: rhs/brick1/d1r13/dir/f.100
trusted.afr.dist-rep3-client-0=0x000000000000000000000000
trusted.afr.dist-rep3-client-1=0x000000000000000000000000
trusted.gfid=0xf1250b5f0343495899d1ed6e9a887126
trusted.glusterfs.quota.cc500630-b0af-4198-8d2e-da234ce22db8.contri=0x0000000000a00000
trusted.pgfid.cc500630-b0af-4198-8d2e-da234ce22db8=0x00000001


whereas from nfs mountpoint, if I take the case of file f.100
this is existing,
[root@rhsauto030 dir]# ls -l f.100
-rw-r--r--. 1 root root 10485760 Oct 11  2013 f.100
[root@rhsauto030 dir]# pwd
/mnt/nfs-test/dir
[root@rhsauto030 dir]# mount | grep dist-rep3
10.70.42.186:dist-rep3 on /mnt/nfs-test type nfs (rw,addr=10.70.42.186)

Expected results:
just creating should not result in any "E" msgs.

Additional info: