Hi, I have problem with glusterfs 3.3.0. I have 4 node cluster with several volumes. All bricks are ext4 filesystem, no selinux and writing extended attributes with setfattr works fine. But in brick logs I see messages like this: [2012-09-13 12:50:17.428402] E [posix.c:857:posix_mknod] 0-bacula-strip-posix: setting xattrs on /mnt/bacula/fff failed (Operation not supported) everytime I create some file on mounted volume. Glusterfs was upgraded from version 3.2.1. This error I can see on replicated volume which was there from version 3.2.1 and on stripe volume which was created after upgrade to 3.3.0. But on one-brick volume this error doesn't appear. On stripe volume there is some other strange behaviour but I think it's related to this xattr issue. On created file with getfattr I can see set attribute trusted.gfid. On volume itself are attributes trusted.gfid and trusted.glusterfs.volume-id. According to log it seems that this problem starts after upgrade to 3.3.0. On 3.2.1 version there wasn't these errors in logs. Could you please help me with solving this problem? Thanks, -- Jan Krajdl
Bump. Anybody hasn't any idea? It's quite critical for me and I don't known what to try next... Thanks, -- Jan Krajdl Dne 13.9.2012 23:54, Jan Krajdl napsal(a):> Hi, > > I have problem with glusterfs 3.3.0. I have 4 node cluster with several > volumes. All bricks are ext4 filesystem, no selinux and writing extended > attributes with setfattr works fine. But in brick logs I see messages > like this: > [2012-09-13 12:50:17.428402] E [posix.c:857:posix_mknod] > 0-bacula-strip-posix: setting xattrs on /mnt/bacula/fff failed > (Operation not supported) > everytime I create some file on mounted volume. Glusterfs was upgraded > from version 3.2.1. This error I can see on replicated volume which was > there from version 3.2.1 and on stripe volume which was created after > upgrade to 3.3.0. But on one-brick volume this error doesn't appear. On > stripe volume there is some other strange behaviour but I think it's > related to this xattr issue. > > On created file with getfattr I can see set attribute trusted.gfid. On > volume itself are attributes trusted.gfid and > trusted.glusterfs.volume-id. According to log it seems that this problem > starts after upgrade to 3.3.0. On 3.2.1 version there wasn't these > errors in logs. > > Could you please help me with solving this problem? Thanks, > >-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120917/1b29912b/attachment.sig>
Hi, ubuntu 12.04.01 LTS 64bit openstack Essex glusterFS 3.3 We gave 2 openstack nodes which glusterfs share on /var/lib/nova/instances When I put a lot of network traffic (100Mbps) to 1 or more instances on the openstack nodes, the instances stop responding after some time (+/- 20min). I can not connect with VNC or which ssh to the intances that do not response, only after a reboot of the instance, everthing starts working again. I guess it has something to do with the network load on the instances, this because other instances keep working. How can I debug this of better solve this issue? Grtz, Jiri Hoogeveen