Re: [Gluster-users] GlusterFS over S3FS
Vincent Miszczak [2016-06-15 10:27 +] : > I would like to combine Glusterfs with S3FS. [...] > I also have the idea to test this with Swift object storage. Advises are > welcome. Never tried this before. Maybe S3QL [1] works since it "is a standard conforming, full featured UNIX file system that is conceptually indistinguishable from any local file system". 1: https://bitbucket.org/nikratio/s3ql/ The entire approach sounds a bit hackish to me though. :-) Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Gluster update
Gandalf Corvotempesta [2016-05-27 13:18 +0200] : > and the recommended way is to shut everything down as the rolling > update states: "feel adventurous" I just read that... Anyway, I hope that it's possible. I'm with you since I don't see a point in a clustered file system if you can't take a node down by plan. Not only to upgrade GlusterFS, but the entire system. Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Gluster update
Niklaas Baudet von Gersdorff [2016-05-27 13:12 +0200] : > Gandalf Corvotempesta [2016-05-27 12:17 +0200] : > > > Please read this: > > http://www.gluster.org/community/documentation/index.php/Upgrade_to_3.7 > > > > "GlusterFS upgrade to 3.7.x > > "a) Scheduling a downtime > > For this approach, schedule a downtime and prevent all your clients > > from accessing (umount your volumes, stop gluster Volumes..etc)the > > servers." > > On the website there a options a (the one you quoted) *and b*. The > second option says > > b) Rolling Upgrade [TBD] > > I guess, this can be translated in two ways. First, at this stage is it > not possible to perform a rolling upgrade. Because of this, this is > something that needs to be worked on (to be done). Or, second, it is > indeed possible to perform a rolling upgrade. Nonetheless, we still have > to document here how to do; this documentation needs to be done. > > Just my two cents. Please see http://www.gluster.org/community/documentation/index.php/Upgrade_to_3.5 where it's documented how to perform a rolling upgrade. This is for 3.5 but maybe you can adapt this procedure (in hope that the feature "performing rolling upgrades" didn't become abandoned in more recent versions). That was my third cent. Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Gluster update
Gandalf Corvotempesta [2016-05-27 12:17 +0200] : > Please read this: > http://www.gluster.org/community/documentation/index.php/Upgrade_to_3.7 > > "GlusterFS upgrade to 3.7.x > "a) Scheduling a downtime > For this approach, schedule a downtime and prevent all your clients > from accessing (umount your volumes, stop gluster Volumes..etc)the > servers." On the website there a options a (the one you quoted) *and b*. The second option says b) Rolling Upgrade [TBD] I guess, this can be translated in two ways. First, at this stage is it not possible to perform a rolling upgrade. Because of this, this is something that needs to be worked on (to be done). Or, second, it is indeed possible to perform a rolling upgrade. Nonetheless, we still have to document here how to do; this documentation needs to be done. Just my two cents. Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] file permissions for shared access
Ryan Brothers [2016-05-25 14:38 -0400] : > I am mounting a gluster volume on several clients for shared access. > The uid's and gid's of the users and groups do not match on each of > the clients, so a given user could have a different uid on each > client. I am not a professional, so take the following advice with a grain of salt: Have you thought about using bindfs [1] to map uid and gid as needed? 1: http://bindfs.org/ Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] 0-management: argument invalid
Atin Mukherjee [2016-05-25 18:30 +0530] : > It seems like 24007 port is blocked by firewall. Also brick process > starts binding from port 49152, so you may have to open up those ports too. I can confirm that it was related to some firewall/network related issue. I could eventually solve the problem. Thanks again! Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] 0-management: argument invalid
Niklaas Baudet von Gersdorff [2016-05-25 13:59 +0200] : > To me it looks like a firewall issue since there's a problem > establishing a connection (see line 2 and three). Yet, IP 10.1.0.1 is > on an internal interface that is not protected by firewall: I just figured out that it's indeed a problem with the firewall. So the problem should be solved once I set up the firewall correctly. > Maybe that's causing some issues. How can I force the daemon to only > listen to IP 10.1.0.1? Anyway, I will be happy if someone can provide me the answer to the question above. I prefer services not to listen on every IP address. Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] 0-management: argument invalid
Atin Mukherjee [2016-05-25 15:50 +0530] : > Could you check the brick log? Sorry, I was not aware of the fact that there is an additional log. Here it is: [2016-05-25 08:26:11.830795] I [MSGID: 100030] [glusterfsd.c:2318:main] 0-/usr/local/sbin/glusterfsd: Started running /usr/local/sbin/glusterfsd version 3.7.6 (args: /usr/local/sbin/glusterfsd -s box-fra-01.klaas --volfile-id volume1.box-fra-01.klaas.usr-local-glusterfs-volume1 -p /var/db/glusterd/vols/volume1/run/box-fra-01.klaas-usr-local-glusterfs-volume1.pid -S /var/run/gluster/f816ca60d4f69f995e570ed408036266.socket --brick-name /usr/local/glusterfs/volume1 -l /var/log/glusterfs/bricks/usr-local-glusterfs-volume1.log --xlator-option *-posix.glusterd-uuid=2a95ee7c-bfb7-4acd-b029-42da963d5862 --brick-port 49153 --xlator-option volume1-server.listen-port=49153) [2016-05-25 08:27:26.838921] E [socket.c:2278:socket_connect_finish] 0-glusterfs: connection to 10.1.0.1:24007 failed (Operation timed out) [2016-05-25 08:27:26.839707] E [glusterfsd-mgmt.c:1818:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: box-fra-01.klaas (Connection reset by peer) [2016-05-25 08:27:26.839756] I [glusterfsd-mgmt.c:1824:mgmt_rpc_notify] 0-glusterfsd-mgmt: Exhausted all volfile servers [2016-05-25 08:27:26.840712] W [glusterfsd.c:1236:cleanup_and_exit] (-->0x40d0a0 at /usr/local/sbin/glusterfsd -->0x4079ed at /usr/local/sbin/glusterfsd ) 0-: received signum (1), shutting down [2016-05-25 08:27:26.848019] W [rpc-clnt.c:1586:rpc_clnt_submit] 0-glusterfs: failed to submit rpc-request (XID: 0x1 Program: Gluster Portmap, ProgVers: 1, Proc: 5) to rpc-transport (glusterfs) To me it looks like a firewall issue since there's a problem establishing a connection (see line 2 and three). Yet, IP 10.1.0.1 is on an internal interface that is not protected by firewall: tap0: flags=8943 metric 0 mtu 1500 options=8 ether 00:bd:17:0f:00:00 inet6 fd16:dcc0:f4cc::1:0:1 prefixlen 80 inet6 fe80::2bd:17ff:fe0f:0%tap0 prefixlen 64 scopeid 0x4 inet 10.1.0.1 netmask 0xff00 broadcast 10.255.255.255 nd6 options=21 media: Ethernet autoselect status: active Opened by PID 10208 Further, I noticed that the daemon listens on every IP address: USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root glusterfsd 27595 11 tcp4 *:24007 *:* Maybe that's causing some issues. How can I force the daemon to only listen to IP 10.1.0.1? Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] 0-management: argument invalid
Hello, on a FreeBSD 10.3 machine I get the following error if I try to start a volume with `gluster volume start volume1`: [2016-05-25 08:26:11.807056] W [common-utils.c:1685:gf_string2boolean] (-->0x8048d84e4 at /usr/local/lib/glusterfs/3.7.6/xlator/mgmt/glusterd.so -->0x800870f6b at /usr/local/lib/libglusterfs.so.0 ) 0-management: argument invalid [Invalid argument] [2016-05-25 08:27:26.845925] E [MSGID: 106005] [glusterd-utils.c:4534:glusterd_brick_start] 0-management: Unable to start brick box-fra-01.klaas:/usr/local/glusterfs/volume1 [2016-05-25 08:27:26.847596] E [MSGID: 106123] [glusterd-syncop.c:1404:gd_commit_op_phase] 0-management: Commit of operation 'Volume Start' failed on localhost The first warning appears immediately after I issue the command. As the timestamp reveals, the command remains idle for quite some time. This is how I created the volume: $ gluster volume create volume1 replica 2 transport tcp box-fra-01.klaas:/usr/local/glusterfs/volume1 box-ams-01.klaas:/usr/local/glusterfs/volume1 force volume create: volume1: success: please start the volume to access data This is the version of gluster that is installed: $ pkg info | grep gluster glusterfs-3.7.6GlusterFS distributed file system Any help is appreciated. Niklaas signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
