Hello Amar. I have reproduced the issue once again and posted the log here: http://glusterfs.pastebin.com/7WpU8hG5 Let me know if you need more information or want me to test something. Thanks, Alessandro On Tue, Dec 14, 2010 at 1:55 PM, Amar Tumballi <amar at gluster.com> wrote: > Hi Alessandro, > We found that there are some issues with 'gf_log' format in few of the > corner case logs. They are being reviewed, once they are inside the > repository, I will let you know. Can you send the log for this crash? so we > can be sure its fixed when we make next release? > Regards, > Amar > > On Tue, Dec 14, 2010 at 5:21 PM, Alessandro Iurlano > <alessandro.iurlano at gmail.com> wrote: >> >> Hello again Amar. >> >> I have managed to try the latest commit from >> git://git.gluster.com/glusterfs >> The problem happened again though this time it lasted much longer, >> allowing me to do an apt-get upgrade and some other minor things. But >> then the container stopped working and I get Transport endpoint is not >> connected. >> >> I am using a mixed environment for the tests. In particular, due to >> hardware shortage, the gluster and OpenVz server is a 64bit machine >> and the other gluster server is an old Pentium4 32bit only. Could this >> mixed 32/64 bit environment be related? >> >> Thanks for any help, >> Alessandro >> >> On Mon, Dec 13, 2010 at 3:48 PM, Alessandro Iurlano >> <alessandro.iurlano at gmail.com> wrote: >> > Hello Amar. >> > >> > I have just tried version 3.1.2qa2 but the problem is still there. >> > Should I download the git version? If so, could you provide the git >> > url of the latest version? >> > >> > Thanks, >> > Alessandro >> > >> > On Mon, Dec 13, 2010 at 3:04 PM, Amar Tumballi <amar at gluster.com> wrote: >> >> Hi Alessandro, >> >> >> >>>> This is an extract from an error log?http://pastebin.com/66ipxbnA >> >> >> >> Thanks for the bug report. We found the reason for the crash reported, >> >> and >> >> fixes are already in repository. You can either wait for newer release, >> >> or >> >> checkout the latest repository code for the fix. >> >> Regards, >> >> Amar >> >> >> >> On Fri, Dec 10, 2010 at 4:38 PM, Alessandro Iurlano >> >> <alessandro.iurlano at gmail.com> wrote: >> >>> >> >>> Hello everybody >> >>> >> >>> I am evaluating Gluster as storage backend for our virtualization >> >>> infrastructure but I am having problems using Glusterfs with OpenVZ. >> >>> What I want to do is to store OpenVZ containers on Glusterfs >> >>> filesystem and not to mount Glusterfs volumes from inside OpenVZ >> >>> containers that appears to be what everyone does, according to Google >> >>> results. >> >>> >> >>> Basically I have setup an OpenVZ server (with Proxmox) and a >> >>> replicated Glusterfs volume from that server and another debian >> >>> machine. >> >>> I have been able to create an OpenVZ container on the Glusterfs >> >>> filesystem without problems with the latest Glusterfs version 3.1.2qa1 >> >>> (due to the mknod bug >> >>> http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2145). But >> >>> whenever I start this new container it lasts only a couple of minutes >> >>> (just the time to boot and a couple commands) and then Glusterfs hangs >> >>> and I get the error Transport Endpoint is not connected. >> >>> >> >>> The Gluster volume is not accessible anymore from the OpenVz server >> >>> (even though this server is a gluster server itself), the container >> >>> completely stops working and killing glusterfs processes does not help >> >>> to recover the situation. The only way is to reboot the machine. >> >>> >> >>> This is an extract from an error log http://pastebin.com/66ipxbnA >> >>> >> >>> Any suggestions? >> >>> Does anybody have any successful experience with OpenVZ and Gluster or >> >>> know of any howto / documentation? >> >>> >> >>> Thanks in advance, >> >>> Alessandro >> >>> _______________________________________________ >> >>> Gluster-users mailing list >> >>> Gluster-users at gluster.org >> >>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> >> >> >> >> > > >
