Gluster users - May 2012 - How to set backup volume server in mount options

Hi,
I saw in the 3.3 changelog that now it is possible to set a secondary 
server to retrieve the volume information from, when mounting a volume 
via the native client.

However... I can't find any documentation in the man pages explaining 
how to do this.

Currently I have:

mount -t glusterfs storage01:/testvol /mnt/somewhere

I guess I need to add -o backup-volume=storage02 or something?


-Toby

On 04/05/12 11:35, Toby Corkindale wrote:
> Hi,
> I saw in the 3.3 changelog that now it is possible to set a secondary
> server to retrieve the volume information from, when mounting a volume
> via the native client.
>
> However... I can't find any documentation in the man pages explaining
> how to do this.
>
> Currently I have:
>
> mount -t glusterfs storage01:/testvol /mnt/somewhere
>
> I guess I need to add -o backup-volume=storage02 or something?
I dug this option out of the source code, *but it still doesn't work*:

mount -t glusterfs -o backupvolfile-server=storage02 storage01:/testvol 
/mnt/somewhere

Didn't send to the list :(

On Fri, May 4, 2012 at 11:07 AM, Kaushal M <kshlmster at gmail.com> wrote:
> Hi Toby.
>
> This is the correct way to do it and it should work.
>
> However, there was a bug reported earlier where the outputs of mount/df
> command showed the original server even when the backup server was used for
> gluster mounts. This bug doesn't happen anymore on the latest qa
release.
>
> I believe you are testing with 3.3 beta 3. Could you check with the latest
> 3.3.0qa release (src tarball here
>
http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.3.0qa39.tar.gz, no
debs) and see if the problem still exists?
>
> Thanks,
> Kaushal
>
> On Fri, May 4, 2012 at 7:15 AM, Toby Corkindale <
> toby.corkindale at strategicdata.com.au> wrote:
>
>> On 04/05/12 11:35, Toby Corkindale wrote:
>>
>>> Hi,
>>> I saw in the 3.3 changelog that now it is possible to set a
secondary
>>> server to retrieve the volume information from, when mounting a
volume
>>> via the native client.
>>>
>>> However... I can't find any documentation in the man pages
explaining
>>> how to do this.
>>>
>>> Currently I have:
>>>
>>> mount -t glusterfs storage01:/testvol /mnt/somewhere
>>>
>>> I guess I need to add -o backup-volume=storage02 or something?
>>>
>>
>> I dug this option out of the source code, *but it still doesn't
work*:
>>
>> mount -t glusterfs -o backupvolfile-server=storage02 storage01:/testvol
>> /mnt/somewhere
>
>
>> ______________________________**_________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>>
http://gluster.org/cgi-bin/**mailman/listinfo/gluster-users<http://gluster.org/cgi-bin/mailman/listinfo/gluster-users>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120504/115d56cb/attachment.html>

On 04/05/12 15:37, Kaushal M wrote:
> Hi Toby.
>
> This is the correct way to do it and it should work.
>
> However, there was a bug reported earlier where the outputs of mount/df
> command showed the original server even when the backup server was used
> for gluster mounts. This bug doesn't happen anymore on the latest qa
> release.
Hi Kaushal,
I don't think that's the same bug. I can't even mount it. (There is 
nothing listed in /proc/mounts, for instance)
> I believe you are testing with 3.3 beta 3. Could you check with the
> latest 3.3.0qa release (src tarball here
>
http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.3.0qa39.tar.gz
> , no debs) and see if the problem still exists?
Ah, ok, I'll have a go with that -- do I need that on the servers too, 
or just the client?

-Toby

On 05/03/12 18:35, Toby Corkindale wrote:
> Hi,
> I saw in the 3.3 changelog that now it is possible to set a secondary
> server to retrieve the volume information from, when mounting a volume
> via the native client.
My brick servers are all on the same subnet. So I actually have a VIP 
controlled by VRRP (keepalived) that I use as the volfile server.

-- 
Mr. Flibble
King of the Potato People

On 04/05/12 17:53, Amar Tumballi wrote:
>> 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version
>> 3.3.0qa39
>> [2012-05-04 17:21:47.918568] E [fuse-bridge.c:4444:init] 0-fuse:
>> Mountpoint gluster seems to have a stale mount, run 'umount
gluster' and
>> try again.
>
> Hi Toby,
>
> Thanks for the log, can you try with below patch and see if it works?
Hi Amar,
Sorry for the delay in responding.

I've tried with the patch, below. It seems to be successful!

>
> ------------
> diff --git a/xlators/mount/fuse/utils/mount.glusterfs.in
> b/xlators/mount/fuse/utils/mount.glusterfs.in
> index aef0939..cb6d36c 100755
> --- a/xlators/mount/fuse/utils/mount.glusterfs.in
> +++ b/xlators/mount/fuse/utils/mount.glusterfs.in
> @@ -166,6 +166,7 @@ start_glusterfs ()
>
> # retry the failover
> if [ $inode -ne 1 ]; then
> + umount $mount_point;
> if [ -n "$cmd_line1" ]; then
> cmd_line1=$(echo "$cmd_line1 $mount_point");
> $cmd_line1
>
> -----------
>
> You can manually modify the /sbin/mount.glusterfs file, and see if it
> works.
>
> Thanks for your patience, and testing :-)
>
> Regards,
> Amar

-- 
.signature