Directly editing the files on backend is not supported. Most of the editors delete the original file and create a new-one when you edit a file. So the extended attributes that are stored on the old-file are gone. Pranith ----- Original Message ----- From: "Daniel M?ller" <mueller at tropenklinik.de> To: "Pranith Kumar. Karampuri" <pranithk at gluster.com> Cc: gluster-users at gluster.org Sent: Wednesday, March 9, 2011 2:24:14 PM Subject: AW: Strange behaviour glusterd 3.1 Both server running. I edit the file on one node1-server (in /mnt/glusterfs/) changed the content, saved the file. Ssh to the node2-server there still old content. Did " find /mnt/glusterfs -print0 | xargs --null stat >/dev/null", still the same old content. Need to restart both servers the the new content is written to node2-server. And this equal behavior on both servers. A few days ago all was ok. ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet: www.tropenklinik.de ----------------------------------------------- -----Urspr?ngliche Nachricht----- Von: Pranith Kumar. Karampuri [mailto:pranithk at gluster.com] Gesendet: Mittwoch, 9. M?rz 2011 09:31 An: mueller at tropenklinik.de Cc: gluster-users at gluster.org Betreff: Re: Strange behaviour glusterd 3.1 "But after vim one.txt and changing the content of that file on one node.", what exactly do you mean by this?. Did you edit the file on backend?. (or) Brought one server down and after editing brought the second server back up?. Pranith ----- Original Message ----- From: "Daniel M?ller" <mueller at tropenklinik.de> To: gluster-users at gluster.org Sent: Wednesday, March 9, 2011 1:58:39 PM Subject: Strange behaviour glusterd 3.1 Dear all, after some weeks of testing gluster the replication of my two nodes stopped working the way it used to be. My version: glusterfs --version glusterfs 3.1.0 built on Oct 13 2010 10:06:10 Repository revision: v3.1.0 Copyright (c) 2006-2010 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU Affero General Public License My Nodes: gluster peer status Number of Peers: 1 Hostname: 192.168.132.56 Uuid: 5ecf561e-f766-48b0-836f-17624586a39a State: Peer in Cluster (Connected) My replicating VOLS: gluster peer status Number of Peers: 1 Hostname: 192.168.132.56 Uuid: 5ecf561e-f766-48b0-836f-17624586a39a State: Peer in Cluster (Connected) [root at ctdb2 test]# gluster volume info Volume Name: samba-vol Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: 192.168.132.56:/glusterfs/export Brick2: 192.168.132.57:/glusterfs/export Options Reconfigured: network.ping-timeout: 5 Now my mount point for the client is /mnt/glusterfs in fstab: 192.168.132.57:/samba-vol /mnt/glusterfs glusterfs defaults 0 0 Commandline mount succeeds with: glusterfs#192.168.132.57:/samba-vol on /mnt/glusterfs type fuse (rw,allow_other,default_permissions,max_read=131072) Now glusterd worked for many weeks. But now when I create a file (ex: one.txt) in /mnt/glusterfs/ the file is replicated to the other node well. But after vim one.txt and changing the content of that file on one node. The changes are not replicated to the other node Until I restart both nodes. I did made a " find /mnt/glusterfs -print0 | xargs --null stat >/dev/null" with no success. Any Idea??? Greetings Daniel ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet: www.tropenklinik.de ----------------------------------------------- _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
