Re: [Gluster-users] backupvolfile-server on 3.5
Excellent. That explains it all and I do see multiple --volfile-server's on the ps output. root 17164 1 0 07:44 ?00:00:00 /usr/sbin/glusterfs --volfile-server=10.31.8.181 --volfile-server=10.31.8.186 --volfile-id=/ov1data1 /mnt Many thanks, Simon -Original Message- From: Kaushal M [mailto:kshlms...@gmail.com] Sent: 18 June 2014 12:56 To: Simon Barrett Cc: Humble Devassy Chirammal; gluster-users@gluster.org Subject: Re: [Gluster-users] backupvolfile-server on 3.5 The mount-options shown in the mount command are the filesystem options that have been passed to the fuse kernel module from the glusterfs client process. The backup-volfile-servers option is not really a filesystem option in general sense, and is only understood by the glusterfs client process. So it's not passed to fuse. (I also believe that fuse will reject any such option if passed, but I am not a 100% sure.) There are several other such options that don't show up. If you want to check actually confirm whether the options is being used or not, you can check the command line used to launch the client process using ps/pgrep etc. The command line will be similar to '/usr/local/sbin/glusterfs --volfile-server=172.17.0.3 --volfile-server=172.17.0.2 --volfile-id=/test /mnt' ~kaushal On Wed, Jun 18, 2014 at 5:16 PM, Simon Barrett wrote: > Thanks. I did see that mentioned in some postings but although it does > not complain about that mount option when I try it, I still don’t see > it listed on the mounted filesystem. I just see the defaults: > > > > root@host> mount -t glusterfs -o backup-volfile-servers=10.31.8.186 > 10.31.8.181:/ov1data1 /mnt > > root@host> mount | grep ov1data1 > > 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs > (rw,default_permissions,allow_other,max_read=131072) > > > > Simon > > > > From: Humble Devassy Chirammal [mailto:humble.deva...@gmail.com] > Sent: 18 June 2014 12:37 > To: Simon Barrett > Cc: gluster-users@gluster.org > Subject: Re: [Gluster-users] backupvolfile-server on 3.5 > > > > Hi Simon, > > In latest versions of glusterfs , 'backupvolfile-server' has changed > to 'backup-volfile-servers' . > > --Humble > > > > > > > > On Wed, Jun 18, 2014 at 3:39 PM, Simon Barrett > wrote: > > Can anyone please comfirm the correct syntax for defining a backup > volfile server? Or is this no longer needed in 3.5 (which I think this > is > suggesting: https://bugzilla.redhat.com/show_bug.cgi?id=986429). > > > > > > I try this and don’t get any errors from the mount command: > > > > root@host> mount -t glusterfs -o backupvolfile-server=10.31.8.186 > 10.31.8.181:/ov1data1 /mnt > > > > But when I check the mount, I don’t see the option displayed: > > > > root@host> mount | grep data1 > > 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs > (rw,default_permissions,allow_other,max_read=131072) > > > > The system itself is CentOS 6.5 and I am running the following rpm versions: > > > > root@host> rpm -qa | grep gluster > > glusterfs-fuse-3.5.0-2.el6.x86_64 > > glusterfs-libs-3.5.0-2.el6.x86_64 > > glusterfs-cli-3.5.0-2.el6.x86_64 > > vdsm-gluster-4.14.9-0.el6.noarch > > glusterfs-rdma-3.5.0-2.el6.x86_64 > > glusterfs-server-3.5.0-2.el6.x86_64 > > glusterfs-3.5.0-2.el6.x86_64 > > glusterfs-api-3.5.0-2.el6.x86_64 > > > > > > Many thanks, > > > > Simon > > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users > > > > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] backupvolfile-server on 3.5
The mount-options shown in the mount command are the filesystem options that have been passed to the fuse kernel module from the glusterfs client process. The backup-volfile-servers option is not really a filesystem option in general sense, and is only understood by the glusterfs client process. So it's not passed to fuse. (I also believe that fuse will reject any such option if passed, but I am not a 100% sure.) There are several other such options that don't show up. If you want to check actually confirm whether the options is being used or not, you can check the command line used to launch the client process using ps/pgrep etc. The command line will be similar to '/usr/local/sbin/glusterfs --volfile-server=172.17.0.3 --volfile-server=172.17.0.2 --volfile-id=/test /mnt' ~kaushal On Wed, Jun 18, 2014 at 5:16 PM, Simon Barrett wrote: > Thanks. I did see that mentioned in some postings but although it does not > complain about that mount option when I try it, I still don’t see it listed > on the mounted filesystem. I just see the defaults: > > > > root@host> mount -t glusterfs -o backup-volfile-servers=10.31.8.186 > 10.31.8.181:/ov1data1 /mnt > > root@host> mount | grep ov1data1 > > 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs > (rw,default_permissions,allow_other,max_read=131072) > > > > Simon > > > > From: Humble Devassy Chirammal [mailto:humble.deva...@gmail.com] > Sent: 18 June 2014 12:37 > To: Simon Barrett > Cc: gluster-users@gluster.org > Subject: Re: [Gluster-users] backupvolfile-server on 3.5 > > > > Hi Simon, > > In latest versions of glusterfs , 'backupvolfile-server' has changed to > 'backup-volfile-servers' . > > --Humble > > > > > > > > On Wed, Jun 18, 2014 at 3:39 PM, Simon Barrett > wrote: > > Can anyone please comfirm the correct syntax for defining a backup volfile > server? Or is this no longer needed in 3.5 (which I think this is > suggesting: https://bugzilla.redhat.com/show_bug.cgi?id=986429). > > > > > > I try this and don’t get any errors from the mount command: > > > > root@host> mount -t glusterfs -o backupvolfile-server=10.31.8.186 > 10.31.8.181:/ov1data1 /mnt > > > > But when I check the mount, I don’t see the option displayed: > > > > root@host> mount | grep data1 > > 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs > (rw,default_permissions,allow_other,max_read=131072) > > > > The system itself is CentOS 6.5 and I am running the following rpm versions: > > > > root@host> rpm -qa | grep gluster > > glusterfs-fuse-3.5.0-2.el6.x86_64 > > glusterfs-libs-3.5.0-2.el6.x86_64 > > glusterfs-cli-3.5.0-2.el6.x86_64 > > vdsm-gluster-4.14.9-0.el6.noarch > > glusterfs-rdma-3.5.0-2.el6.x86_64 > > glusterfs-server-3.5.0-2.el6.x86_64 > > glusterfs-3.5.0-2.el6.x86_64 > > glusterfs-api-3.5.0-2.el6.x86_64 > > > > > > Many thanks, > > > > Simon > > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users > > > > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] backupvolfile-server on 3.5
Thanks. I did see that mentioned in some postings but although it does not complain about that mount option when I try it, I still don’t see it listed on the mounted filesystem. I just see the defaults: root@host> mount -t glusterfs -o backup-volfile-servers=10.31.8.186 10.31.8.181:/ov1data1 /mnt root@host> mount | grep ov1data1 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072) Simon From: Humble Devassy Chirammal [mailto:humble.deva...@gmail.com] Sent: 18 June 2014 12:37 To: Simon Barrett Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] backupvolfile-server on 3.5 Hi Simon, In latest versions of glusterfs , 'backupvolfile-server' has changed to 'backup-volfile-servers' . --Humble On Wed, Jun 18, 2014 at 3:39 PM, Simon Barrett mailto:simon.barr...@tradingscreen.com>> wrote: Can anyone please comfirm the correct syntax for defining a backup volfile server? Or is this no longer needed in 3.5 (which I think this is suggesting: https://bugzilla.redhat.com/show_bug.cgi?id=986429). I try this and don’t get any errors from the mount command: root@host> mount -t glusterfs -o backupvolfile-server=10.31.8.186 10.31.8.181:/ov1data1 /mnt But when I check the mount, I don’t see the option displayed: root@host> mount | grep data1 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072) The system itself is CentOS 6.5 and I am running the following rpm versions: root@host> rpm -qa | grep gluster glusterfs-fuse-3.5.0-2.el6.x86_64 glusterfs-libs-3.5.0-2.el6.x86_64 glusterfs-cli-3.5.0-2.el6.x86_64 vdsm-gluster-4.14.9-0.el6.noarch glusterfs-rdma-3.5.0-2.el6.x86_64 glusterfs-server-3.5.0-2.el6.x86_64 glusterfs-3.5.0-2.el6.x86_64 glusterfs-api-3.5.0-2.el6.x86_64 Many thanks, Simon ___ Gluster-users mailing list Gluster-users@gluster.org<mailto:Gluster-users@gluster.org> http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] backupvolfile-server on 3.5
Hi Simon, In latest versions of glusterfs , 'backupvolfile-server' has changed to 'backup-volfile-servers' . --Humble On Wed, Jun 18, 2014 at 3:39 PM, Simon Barrett < simon.barr...@tradingscreen.com> wrote: > Can anyone please comfirm the correct syntax for defining a backup > volfile server? Or is this no longer needed in 3.5 (which I think this is > suggesting: https://bugzilla.redhat.com/show_bug.cgi?id=986429). > > > > > > I try this and don’t get any errors from the mount command: > > > > root@host> mount -t glusterfs -o backupvolfile-server=10.31.8.186 > 10.31.8.181:/ov1data1 /mnt > > > > But when I check the mount, I don’t see the option displayed: > > > > root@host> mount | grep data1 > > 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs > (rw,default_permissions,allow_other,max_read=131072) > > > > The system itself is CentOS 6.5 and I am running the following rpm > versions: > > > > root@host> rpm -qa | grep gluster > > glusterfs-fuse-3.5.0-2.el6.x86_64 > > glusterfs-libs-3.5.0-2.el6.x86_64 > > glusterfs-cli-3.5.0-2.el6.x86_64 > > vdsm-gluster-4.14.9-0.el6.noarch > > glusterfs-rdma-3.5.0-2.el6.x86_64 > > glusterfs-server-3.5.0-2.el6.x86_64 > > glusterfs-3.5.0-2.el6.x86_64 > > glusterfs-api-3.5.0-2.el6.x86_64 > > > > > > Many thanks, > > > > Simon > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users > ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] backupvolfile-server on 3.5
Can anyone please comfirm the correct syntax for defining a backup volfile server? Or is this no longer needed in 3.5 (which I think this is suggesting: https://bugzilla.redhat.com/show_bug.cgi?id=986429). I try this and don't get any errors from the mount command: root@host> mount -t glusterfs -o backupvolfile-server=10.31.8.186 10.31.8.181:/ov1data1 /mnt But when I check the mount, I don't see the option displayed: root@host> mount | grep data1 10.31.8.181:/ov1data1 on /mnt type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072) The system itself is CentOS 6.5 and I am running the following rpm versions: root@host> rpm -qa | grep gluster glusterfs-fuse-3.5.0-2.el6.x86_64 glusterfs-libs-3.5.0-2.el6.x86_64 glusterfs-cli-3.5.0-2.el6.x86_64 vdsm-gluster-4.14.9-0.el6.noarch glusterfs-rdma-3.5.0-2.el6.x86_64 glusterfs-server-3.5.0-2.el6.x86_64 glusterfs-3.5.0-2.el6.x86_64 glusterfs-api-3.5.0-2.el6.x86_64 Many thanks, Simon ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
