Re: [Gluster-users] GlusterFS and inotify
On Tue, Jan 26, 2010 at 1:20 AM, Larry Bates wrote: > I recently moved my backend storage to GlusterFS V3.0 and with one exception > everything is running great. That exception is that I had a daemon using > inotify that was watching my storage for new files. Upon arrival this watcher > uploaded a copy of the file to Amazon S3. This daemon had been running just > fine for well over a year. Moving to GlusterFS seems to indicate that inotify > doesn't work on GlusterFS volumes. I don't know if it is a Gluster, Fuse, or > some other problem. inotify just refuses to allow me to register the top > level > folder to be watched. Before I spend a lot of time on this, I thought I'd > bounce it off of the "experts" on this list. > > Anyone have any ideas? This is a limitation in FUSE. Future versions might support it. You can get a definitive answer on the fuse-devel list. Avati ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] minor issue related to the server config doc
On Wed, Feb 3, 2010 at 7:56 PM, Daniel Maher > wrote: > Hi all, > > This is a minor issue related to the server config documentation on the > Gluster website : > > http://www.gluster.com/community/documentation/index.php/Storage_Server_Installation_and_Configuration > > The documentation suggests using the gluster-volgen tool in order to create > the configuration files (which works well enough), but then goes on to > suggest that once the configurations have been generated that the next step > is starting the glusterfsd service. > > If you follow those steps precisely, it won't work - for example : > > [r...@s01 glusterfs]# service glusterfsd start > Starting glusterfsd: > /etc/glusterfs/glusterfsd.vol: No such file or directory > Try `/usr/sbin/glusterfsd --help' or `/usr/sbin/glusterfsd --usage' for > more information. > > Perhaps the documentation could be altered in order to note that either: > a) The generated configuration file needs to be renamed > b) The actual name of the configuration file needs to be passed to the > daemon during startup (by editing the init script, for example) > > It's a minor thing, but hey, clarity is important. > > Daniel, Thanks for pointing it out, Its fixed now. - Harshavardhana > > -- > Daniel Maher > ___ > 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] minor issue related to the server config doc
Hi all, This is a minor issue related to the server config documentation on the Gluster website : http://www.gluster.com/community/documentation/index.php/Storage_Server_Installation_and_Configuration The documentation suggests using the gluster-volgen tool in order to create the configuration files (which works well enough), but then goes on to suggest that once the configurations have been generated that the next step is starting the glusterfsd service. If you follow those steps precisely, it won't work - for example : [r...@s01 glusterfs]# service glusterfsd start Starting glusterfsd: /etc/glusterfs/glusterfsd.vol: No such file or directory Try `/usr/sbin/glusterfsd --help' or `/usr/sbin/glusterfsd --usage' for more information. Perhaps the documentation could be altered in order to note that either: a) The generated configuration file needs to be renamed b) The actual name of the configuration file needs to be passed to the daemon during startup (by editing the init script, for example) It's a minor thing, but hey, clarity is important. -- Daniel Maher ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] GlusterFS vs. NFS
Brian J Mingus wrote: We recently purchased a new cluster and I have been advocating the use of glusterfs. I have a lot of experience on the user side with nfs and my feeling is that it has poor performance. I suggested gluster which got relayed to our vendor and this is what they relayed back to me: - Suggests we stay away from glusterfs and gfs - glusterfs is not mature - We need a stable parallel file system. nfs is stable, glusterfs is not. - Using gluster would be adding complexity and removing reliability. You have all of this hardware, why not test it and prove its utility within your organization? IMO, you have to consider The One Truth about vendors: You can't trust 'em. Personally, I've found NFS to out-perform GlusterFS and on two occasions now have had to switch back to it from a glusterfs rollout. That is likely configuration-dependent though, so it's hard to really point my finger at GlusterFS itself. And it's worth noting that using NFS means I'm not using a parallel filesystem, so there is no redundancy, and redundancy is worth a lot. John -- John Madden Sr UNIX Systems Engineer Ivy Tech Community College of Indiana jmad...@ivytech.edu ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] mount failed
Hi Jass Zhao, Do you have fuse on client machine? Glusterfs requires fuse on client side. try checking it: lsmod | grep fuse and then load it, modprobe fuse. Cheers, Lakshmipathi.G - Original Message - From: "Jass Zhao" To: gluster-users@gluster.org Sent: Wednesday, February 3, 2010 1:30:57 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi Subject: [Gluster-users] mount failed Hi, I tried gluster .3.0 with centos5.2 x86_64. I following the installation guide: * http://www.gluster.com/community/documentation/index.php/GlusterFS_User_Guide * * * *After configuring a distribute volume, the mount failed:** * */usr/bin/glusterfs-volgen --name testvol comp-1:/data/testvol comp-2:/data/testvol * *mount -t glusterfs /etc/glusterfs/testvol-tcp.vol /data//mnt/ * * * *Here is the log: /var/log/glusterfs/data-mnt-.log * * * * Version : glusterfs 3.0.0 built on Dec 8 2009 03:09:12 git: 2.0.1-886-g8379edd Starting Time: 2010-02-03 15:51:31 Command line : /usr/sbin/glusterfs --log-level=NORMAL --volfile-server-port=6996 --volfile-server=compute-5-2 /data2/zhaopeng/mnt/ PID : 32578 System name : Linux Nodename : compute-5-2.local Kernel Release : 2.6.18-92.el5xen Hardware Identifier: x86_64 Given volfile: +--+ 1: ### file: server-volume.vol.sample 2: 3: # 4: ### GlusterFS Server Volume File ## 5: # 6: 7: CONFIG FILE RULES: 8: ### "#" is comment character. 9: ### - Config file is case sensitive 10: ### - Options within a volume block can be in any order. 11: ### - Spaces or tabs are used as delimitter within a line. 12: ### - Multiple values to options will be : delimitted. 13: ### - Each option should end within a line. 14: ### - Missing or commented fields will assume default values. 15: ### - Blank/commented lines are allowed. 16: ### - Sub-volumes should already be defined above before referring. 17: 18: ### Export volume "brick" with the contents of "/home/export" directory. 19: volume brick 20: type storage/posix # POSIX FS translator 21: option directory /home/export # Export this directory 22: end-volume 23: 24: ### Add network serving capability to above brick. 25: volume server 26: type protocol/server 27: option transport-type tcp 28: # option transport-type unix 29: # option transport-type ib-sdp 30: # option transport.socket.bind-address 192.168.1.10 # Default is to listen on all interfaces 31: # option transport.socket.listen-port 6996 # Default is 6996 32: 33: # option transport-type ib-verbs 34: # option transport.ib-verbs.bind-address 192.168.1.10 # Default is to listen on all interfaces 35: # option transport.ib-verbs.listen-port 6996 # Default is 6996 36: # option transport.ib-verbs.work-request-send-size 131072 37: # option transport.ib-verbs.work-request-send-count 64 38: # option transport.ib-verbs.work-request-recv-size 131072 39: # option transport.ib-verbs.work-request-recv-count 64 40: 41: # option client-volume-filename /etc/glusterfs/glusterfs-client.vol 42: subvolumes brick 43: # NOTE: Access to any volume through protocol/server is denied by 44: # default. You need to explicitly grant access through # "auth" 45: # option. 46: option auth.addr.brick.allow * # Allow access to "brick" volume 47: end-volume +--+ [2010-02-03 15:51:31] E [mount.c:510:fuse_mount_sys] glusterfs-fuse: cannot open /dev/fuse (No such device) [2010-02-03 15:51:31] N [mount.c:587:gf_fuse_mount] glusterfs-fuse: direct mount failed (No such device), retry to mount via fusermount [2010-02-03 15:51:31] E [mount.c:611:gf_fuse_mount] glusterfs-fuse: mount failed [2010-02-03 15:51:31] E [xlator.c:838:xlator_init_rec] fuse: Initialization of volume 'fuse' failed, review your volfile again [2010-02-03 15:51:31] E [glusterfsd.c:583:_xlator_graph_init] glusterfs: initializing translator failed * *Has anyone ran into the same problem? * * * *BR, * *Gnep * * * ___ 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] mount failed
Hi, I tried gluster .3.0 with centos5.2 x86_64. I following the installation guide: * http://www.gluster.com/community/documentation/index.php/GlusterFS_User_Guide * * * *After configuring a distribute volume, the mount failed:** * */usr/bin/glusterfs-volgen --name testvol comp-1:/data/testvol comp-2:/data/testvol * *mount -t glusterfs /etc/glusterfs/testvol-tcp.vol /data//mnt/ * * * *Here is the log: /var/log/glusterfs/data-mnt-.log * * * * Version : glusterfs 3.0.0 built on Dec 8 2009 03:09:12 git: 2.0.1-886-g8379edd Starting Time: 2010-02-03 15:51:31 Command line : /usr/sbin/glusterfs --log-level=NORMAL --volfile-server-port=6996 --volfile-server=compute-5-2 /data2/zhaopeng/mnt/ PID : 32578 System name : Linux Nodename : compute-5-2.local Kernel Release : 2.6.18-92.el5xen Hardware Identifier: x86_64 Given volfile: +--+ 1: ### file: server-volume.vol.sample 2: 3: # 4: ### GlusterFS Server Volume File ## 5: # 6: 7: CONFIG FILE RULES: 8: ### "#" is comment character. 9: ### - Config file is case sensitive 10: ### - Options within a volume block can be in any order. 11: ### - Spaces or tabs are used as delimitter within a line. 12: ### - Multiple values to options will be : delimitted. 13: ### - Each option should end within a line. 14: ### - Missing or commented fields will assume default values. 15: ### - Blank/commented lines are allowed. 16: ### - Sub-volumes should already be defined above before referring. 17: 18: ### Export volume "brick" with the contents of "/home/export" directory. 19: volume brick 20: type storage/posix # POSIX FS translator 21: option directory /home/export # Export this directory 22: end-volume 23: 24: ### Add network serving capability to above brick. 25: volume server 26: type protocol/server 27: option transport-type tcp 28: # option transport-type unix 29: # option transport-type ib-sdp 30: # option transport.socket.bind-address 192.168.1.10 # Default is to listen on all interfaces 31: # option transport.socket.listen-port 6996 # Default is 6996 32: 33: # option transport-type ib-verbs 34: # option transport.ib-verbs.bind-address 192.168.1.10 # Default is to listen on all interfaces 35: # option transport.ib-verbs.listen-port 6996 # Default is 6996 36: # option transport.ib-verbs.work-request-send-size 131072 37: # option transport.ib-verbs.work-request-send-count 64 38: # option transport.ib-verbs.work-request-recv-size 131072 39: # option transport.ib-verbs.work-request-recv-count 64 40: 41: # option client-volume-filename /etc/glusterfs/glusterfs-client.vol 42: subvolumes brick 43: # NOTE: Access to any volume through protocol/server is denied by 44: # default. You need to explicitly grant access through # "auth" 45: # option. 46: option auth.addr.brick.allow * # Allow access to "brick" volume 47: end-volume +--+ [2010-02-03 15:51:31] E [mount.c:510:fuse_mount_sys] glusterfs-fuse: cannot open /dev/fuse (No such device) [2010-02-03 15:51:31] N [mount.c:587:gf_fuse_mount] glusterfs-fuse: direct mount failed (No such device), retry to mount via fusermount [2010-02-03 15:51:31] E [mount.c:611:gf_fuse_mount] glusterfs-fuse: mount failed [2010-02-03 15:51:31] E [xlator.c:838:xlator_init_rec] fuse: Initialization of volume 'fuse' failed, review your volfile again [2010-02-03 15:51:31] E [glusterfsd.c:583:_xlator_graph_init] glusterfs: initializing translator failed * *Has anyone ran into the same problem? * * * *BR, * *Gnep * * * ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
