So what I did to make it more secure without my vols being "endpoint not connected" is to run rsync not on my mounted vols but directly on my glusterfs/export and the underlying directories. This seems to be more stable. The only thing I must have a look at, that none of my scripts write to glusterfs/export . In any case there is an urgent need to get this feature "snapshot". ----------------------------------------------- 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: Hans Lambermont [mailto:hans at shapeways.com] Gesendet: Dienstag, 9. April 2013 16:45 An: Daniel M?ller Cc: gluster-users at gluster.org Betreff: Re: Glusterfs gives up with endpoint not connected Hi Daniel, Daniel M?ller wrote on 20130409: > After some testing I found out that my backup using rsync caused the > error 'endpoint not connected'. I see this too from time to time. I have to kill all processes that have an open filedescriptor on the mountpoint, then umount and mount again. > Is there a way to take backup snapshots from the volumes by gluster itself? Not yet, it's on the feature roadmap : http://www.gluster.org/community/documentation/index.php/Features/snapshot -- Hans -- Hans Lambermont | Senior Architect (t) +31407370104 (w) www.shapeways.com
