[Gluster-users] (no subject)
Hi, I have a question regarding glusterfs and replicate. I have a two node setup. The following problem arises: if I create a file on the mount point, then unmount gfs on the 2nd machine, remove the file from the 1st (through the mount point) and brind the mount point on the 2nd machine back up. The file is removed (from the 2nd) if I `ls` the mount point on the 1st machine, the file is created (on the 1st) if I `ls` the mount point on the 2nd. If I update the file instead of removing it, everything goes fine. The file is up-to-date on both machines. I looked at the .landfill directory, but that is only used in a self-heal situation. Is there a way I can work around this? Maybe using the trash translator? Best regards, Jeroen Koekkoek ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] glusterfs client waiting on SYN_SENT to connect...
Just wanted to update you all. Turns out the problem is my Juniper Firewall - sort of. I've created a service in our Juniper that describes "Gluster" and allowed the "tcp session" to never timeout. The problem comes when a server crashes and the TCP connection isn't "cleaned up". It looks like the gluster client always starts using the same outbound (source) TCP port and in our firewall that source/dest port combination is already in use (never times out right) and the firewall isn't allowing it to be created again - so its blocked. So right now if i do a netstat -pan tcp0 1 10.10.10.101:996 10.20.10.102:6996 SYN_SENT23491/glusterfs tcp0 1 10.10.10.101:997 10.20.10.102:6996 SYN_SENT23491/glusterfs tcp0 1 10.10.10.101:100010.20.10.102:6996 SYN_SENT23491/glusterfs tcp0 0 10.10.10.101:100110.20.10.102:6996 ESTABLISHED 23491/glusterfs tcp0 0 10.10.10.101:999 10.20.10.101:6996 ESTABLISHED 23491/glusterfs tcp0 1 10.10.10.101:998 10.20.10.101:6996 SYN_SENT23491/glusterfs tcp0 1 10.10.10.101:100310.20.10.101:6996 SYN_SENT23491/glusterfs tcp0 1 10.10.10.101:100210.20.10.101:6996 SYN_SENT23491/glusterfs Now if i kill the gluster process and restart it againnotice the source port doesn't change... tcp0 1 10.10.10.101:996 10.20.10.102:6996 SYN_SENT23687/glusterfs tcp0 1 10.10.10.101:997 10.20.10.102:6996 SYN_SENT23687/glusterfs tcp0 1 10.10.10.101:100010.20.10.102:6996 SYN_SENT23687/glusterfs tcp0 0 10.10.10.101:100110.20.10.102:6996 ESTABLISHED 23687/glusterfs tcp0 0 10.10.10.101:999 10.20.10.101:6996 ESTABLISHED 23687/glusterfs tcp0 1 10.10.10.101:998 10.20.10.101:6996 SYN_SENT23687/glusterfs tcp0 1 10.10.10.101:100310.20.10.101:6996 SYN_SENT23687/glusterfs tcp0 1 10.10.10.101:100210.20.10.101:6996 SYN_SENT23687/glusterfs Now if i kill and restart a few times...i can get lucky and get a different source port...but you can see i'm still missing a few bricks. tcp0 0 10.10.10.101:994 10.20.10.102:6996 ESTABLISHED 23745/glusterfs tcp0 0 10.10.10.101:995 10.20.10.102:6996 ESTABLISHED 23745/glusterfs tcp0 0 10.10.10.101:998 10.20.10.102:6996 ESTABLISHED 23745/glusterfs tcp0 1 10.10.10.101:100010.20.10.102:6996 SYN_SENT23745/glusterfs tcp0 0 10.10.10.101:997 10.20.10.101:6996 ESTABLISHED 23745/glusterfs tcp0 0 10.10.10.101:996 10.20.10.101:6996 ESTABLISHED 23745/glusterfs tcp0 1 10.10.10.101:100310.20.10.101:6996 SYN_SENT23745/glusterfs tcp0 1 10.10.10.101:100210.20.10.101:6996 SYN_SENT23745/glusterfs Now telnet works always because it always picks a random source port: $ telnet 10.20.10.102 6996 Trying 10.20.10.102... Connected to glusterserver (10.20.10.102). Escape character is '^]'. $ netstat -pan|grep telne tcp0 0 10.10.10.101:58757 10.20.10.102:6996 ESTABLISHED 23622/telnet Why does gluster not use a more random source port?? I'm going to have to dig through the Juniper docs to see if i can manually close an active session (lets hope) which should fix my immediate problem but it doesn't really fix the long term problem. Thoughts? thanks, liam On Fri, Dec 3, 2010 at 6:51 PM, Liam Slusser wrote: > Ah the two different IPs are because I was changing my IPs for this mailing > list and I guess I forgot that one. :) Will try added a static route. > Also going to snoop traffic and see if the gluster client is actually > getting to the server or being blocked by the firewall. Ill letcha all know > what I find. > > Thanks for the ideas. > > Liam > > On Dec 3, 2010 6:32 PM, wrote: >> On Fri, Dec 03, 2010 at 04:25:18PM -0800, Liam Slusser wrote: >>> [r...@client~]# netstat -pan|grep glus >>> tcp 0 1 10.8.10.107:1000 10.8.11.102:6996 SYN_SENT 3385/glusterfs >>> >>> from the gluster client log: >>> >>> However, the port is obviously open... >>> >>> [r...@client~]# telnet 10.8.11.102 6996 >>> Trying 10.2.56.102... >>> Connected to glusterserverb (10.8.11.102). >>> Escape character is '^]'. >>> ^] >>> telnet> close >>> Connection closed. >> >> Looking further... why is your telnet trying 10.2.56.102 when you >> clearly specified 10.8.11.102? Also, what happens if you do a >> specific route for the 10.8.11.0/24 block thru the appropriate gw >> without relying on the
[Gluster-users] how to create a striped with replicated volume
Hi, I know how to create a pure striped volume, but it's not security for this kind of volume. How can I create a striped volume with replicated like RAID1+0? By the way, Can we change the stripe count later after created the striped volume? Thanks in advance! -Bill Chen ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Problem mounting Gluster 3.1 with NFS
Thomas, I will look into that page as I see other items which need to be fixed as well since Gluster doesn't allow you to modify the vol file... -Jacob -Original Message- From: Thomas Riske [mailto:t.ri...@uni-assist.de] Sent: Tuesday, December 14, 2010 3:02 AM To: gluster-users@gluster.org Cc: Jacob Shucart Subject: Re: [Gluster-users] Problem mounting Gluster 3.1 with NFS Jacob, as mentioned in my first post, please take a look at: http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_NFS_ Frequently_Asked_Questions#How_to_export_directories_as_separate_NFS_expor ts.3F Regards, Thomas Am 13.12.2010 17:37, schrieb Jacob Shucart: > Thomas, > > Is there a page in the documentation that mentions subdirectory mounting? > If so, I can correct it. Looking at the page on manually mounting NFS > volumes, it shows that you can mount using hostname:/VOLNAME, but not > subdirectories at the moment. > > http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_Manu > ally_Mounting_Volumes_Using_NFS > > -Jacob > > -Original Message- > From: gluster-users-boun...@gluster.org > [mailto:gluster-users-boun...@gluster.org] On Behalf Of Thomas Riske > Sent: Monday, December 13, 2010 2:35 AM > To: gluster-users@gluster.org > Subject: Re: [Gluster-users] Problem mounting Gluster 3.1 with NFS > > Hello Jacob, > > so the documentation about mounting NFS subdirectorys is wrong for the > current version? > > Regards, > Thomas > > Am 10.12.2010 16:58, schrieb Jacob Shucart: >> Hello, >> >> Gluster 3.1.1 does not support mounting a subdirectory of the volume. >> This is going to be changed in the next release. For now, you could > mount >> 192.168.1.88:/raid, but not /raid/nfstest. >> >> -Jacob >> >> -Original Message- >> From: gluster-users-boun...@gluster.org >> [mailto:gluster-users-boun...@gluster.org] On Behalf Of Joe Landman >> Sent: Friday, December 10, 2010 7:45 AM >> To: gluster-users@gluster.org >> Subject: Re: [Gluster-users] Problem mounting Gluster 3.1 with NFS >> >> On 12/10/2010 10:42 AM, Thomas Riske wrote: >>> Hello, >>> >>> I tried to NFS-mount a gluster-volume using the "normal NFS-way" with >>> the directory-path: >>> >>> mount -t nfs 192.168.1.88:/raid/nfstest /mnt/testmount >>> >>> This gives me only the following error message: >>> >>> mount.nfs: mounting 192.168.1.88:/raid/nfstest failed, reason given by >>> server: No such file or directory >> >> [...] >> >>> Is this a bug in gluster, or am I missing something here? >>> >>> Mounting the Gluster-volume with the volume-name over NFS works... >>> (mount -t nfs 192.168.1.88:/test-nfs /mnt/testmount) >> >> If you created the volume with a name of test-nfs, then thats what >> should show up in your exports >> >> showmount -e 192.168.1.88 >> >> > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] posix: mknod on .. failed: File exists
Hi, On Tue, Dec 14, 2010 at 8:17 PM, Michael Reck wrote: > > Thanks for the Info. > I was looking for the latest code base and it seems that the git is only > 3.1.0. > How do I get the latest code? You can use: $ git clone git://git.gluster.com/glusterfs.git glusterfs.git And login and compile the latest code. Regards, Sachidananda. ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] posix: mknod on .. failed: File exists
Am 13.12.2010 07:54, schrieb sac: Hi Michael. On Fri, Dec 10, 2010 at 4:56 PM, Michael Reck wrote: we have an 3 Nodes gluster Installation. Since start of this gluster we have problems like this: [2010-12-10 07:14:57.210627] E [posix.c:437:posix_lookup] posix: lstat on /backup/mail8-node2/yesteryesterday_root.tgz failed: No data available [2010-12-10 08:14:57.778585] E [posix.c:1084:posix_mknod] posix: mknod on /backup/mysql2/yesterday_root.tgz failed: File exists [2010-12-10 08:14:57.813334] E [posix.c:437:posix_lookup] posix: lstat on /backup/mysql2/yesterday_root.tgz failed: No data available The mknod bug is fixed in the latest code base. And the fix will be available in 3.1.2 version of GlusterFS. Even 3.1.1 does not fix this issue. Regards, Sachidananda. Hi Sachidananda, Thanks for the Info. I was looking for the latest code base and it seems that the git is only 3.1.0. How do I get the latest code? Greets Michael ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
[Gluster-users] NFS mount with AIX, Solaris, HP-UX
Dear all, I currently running the 3.1.2qa2 version on glusterFS and I'm still unable to mount GlusterFS directory on Solaris, AIX and HP-UX client contrary to Linux clients who work well. There is no other nfs server running on my glusterFS server and client, rpcbind is started, "showmount -e" on servers show correct output AND it's working fine on linux client. I'm using the command bellow : Solaris 10 cmd : mount -o proto=tcp,vers=3 nfs://ylal3020:38467:/athena /users/glusterfs_mnt error : command work but when I'm trying to access a file from the mount point (cat,tar...) I got " Input/output error" AIX cmd : mount -o proto=tcp,port=38467 ylal3020:/athena /users/glusterfs_mnt error : command work but when I'm trying to access a file from the mount point (cat,tar...) I got " Input/output error" HP-UX 11.11 cmd : mount -F nfs -o proto=tcp,port=38467 ylal3020:/athena /users/glusterfs_mnt error : nfs mount: get_fh: ylal3020:: RPC: Program not registered nfs mount: get_fh: ylal3020:: RPC: Program not registered nfs mount: retry: retrying(1) for: /users/glusterfs_mnt after 5 seconds => strange because rpcbind is up. Does someone have the same issue ? Thx for your help. Extract of config : Volume Name: athena Type: Distributed-Replicate Status: Stopped Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: ylal3020:/users/exp1 Brick2: yval1010:/users/exp3 Brick3: ylal3030:/users/exp2 Brick4: yval1000:/users/exp4 Options Reconfigured: diagnostics.client-log-level: DEBUG diagnostics.brick-log-level: DEBUG performance.cache-min-file-size: 1KB performance.cache-max-file-size: 200MB network.ping-timeout: 5 performance.cache-size: 1GB performance.write-behind-window-size: 512MB ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Problems with Glusterfs and OpenVz
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 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 > 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 >> 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 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 >> >> 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@gluster.org >> >>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> >> >> >> >> > > > ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Problems with Glusterfs and OpenVz
I too had problems in a mixed/OpenVZ setup recently, but as soon as I started using a 64-bit on all nodes the problems went away. This was using the 3.0.5 branch however. Shain -Original Message- From: gluster-users-boun...@gluster.org on behalf of Alessandro Iurlano Sent: Tue 12/14/2010 6:51 AM To: Amar Tumballi Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] Problems with Glusterfs and OpenVz 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 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 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 >> 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@gluster.org >>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> >> > ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Problems with Glusterfs and OpenVz
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.iurl...@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 > 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 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 > >> 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@gluster.org > >>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > >> > >> > > > ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Problems with Glusterfs and OpenVz
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 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 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 >> 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@gluster.org >>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> >> > ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Gluster 3.1.1 64-bit only?
You can - its just not supported or very well tested. liam On Mon, Dec 13, 2010 at 10:07 AM, Matt Keating wrote: > Will it not run at all if I compile on a 32bit system? > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Problem mounting Gluster 3.1 with NFS
Jacob, as mentioned in my first post, please take a look at: http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_NFS_Frequently_Asked_Questions#How_to_export_directories_as_separate_NFS_exports.3F Regards, Thomas Am 13.12.2010 17:37, schrieb Jacob Shucart: Thomas, Is there a page in the documentation that mentions subdirectory mounting? If so, I can correct it. Looking at the page on manually mounting NFS volumes, it shows that you can mount using hostname:/VOLNAME, but not subdirectories at the moment. http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_Manu ally_Mounting_Volumes_Using_NFS -Jacob -Original Message- From: gluster-users-boun...@gluster.org [mailto:gluster-users-boun...@gluster.org] On Behalf Of Thomas Riske Sent: Monday, December 13, 2010 2:35 AM To: gluster-users@gluster.org Subject: Re: [Gluster-users] Problem mounting Gluster 3.1 with NFS Hello Jacob, so the documentation about mounting NFS subdirectorys is wrong for the current version? Regards, Thomas Am 10.12.2010 16:58, schrieb Jacob Shucart: Hello, Gluster 3.1.1 does not support mounting a subdirectory of the volume. This is going to be changed in the next release. For now, you could mount 192.168.1.88:/raid, but not /raid/nfstest. -Jacob -Original Message- From: gluster-users-boun...@gluster.org [mailto:gluster-users-boun...@gluster.org] On Behalf Of Joe Landman Sent: Friday, December 10, 2010 7:45 AM To: gluster-users@gluster.org Subject: Re: [Gluster-users] Problem mounting Gluster 3.1 with NFS On 12/10/2010 10:42 AM, Thomas Riske wrote: Hello, I tried to NFS-mount a gluster-volume using the "normal NFS-way" with the directory-path: mount -t nfs 192.168.1.88:/raid/nfstest /mnt/testmount This gives me only the following error message: mount.nfs: mounting 192.168.1.88:/raid/nfstest failed, reason given by server: No such file or directory [...] Is this a bug in gluster, or am I missing something here? Mounting the Gluster-volume with the volume-name over NFS works... (mount -t nfs 192.168.1.88:/test-nfs /mnt/testmount) If you created the volume with a name of test-nfs, then thats what should show up in your exports showmount -e 192.168.1.88 ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
[Gluster-users] Cannot add server by using Gluster Platform
Dear all, I have three machine that has three NIC card, I install one of them in GSP Master, but when I want to add server, it shows, 『Installer agent died. Installation aborted』 I login the server and try to find "/tmp/start-server-installer.log”, but there is no such log file, In my suggest, is there any problem about NIC card or my IP setting ? Any suggestion will very thankful. Eames. ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
