[Bugs] [Bug 1208676] New: No support for mounting volumes with volume files
bugzilla at redhat.com
bugzilla at redhat.com
Thu Apr 2 20:04:09 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1208676
Bug ID: 1208676
Summary: No support for mounting volumes with volume files
Product: GlusterFS
Version: 3.6.2
Component: scripts
Severity: urgent
Assignee: bugs at gluster.org
Reporter: ernetas at gmail.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Description of problem:
Mounting a Gluster volume with a volume file was not possible due to a small
bug in mount script:
Version-Release number of selected component (if applicable):
3.6.2 from ppa:gluster/glusterfs-3.6
How reproducible:
By installing latest GlusterFS 3.6 and trying to mount a volume using volume
files.
Steps to Reproduce:
1. Install GlusterFS 3.6.
2. Try mounting volume using Gluster volume file.
Actual results:
root at puppet2:/home/supervisor# mount -t glusterfs /etc/gfs.vol /data2
ERROR: Server name/volume name unspecified cannot proceed further..
Please specify correct format
Usage:
man 8 /sbin/mount.glusterfs
root at puppet2:/home/supervisor# cat /etc/gfs.vol
volume files1
type protocol/client
option transport-type tcp
option remote-host files1.xx.com
option remote-subvolume /data/puppet
end-volume
volume files2
type protocol/client
option transport-type tcp
option remote-host files2.xx.com
option remote-subvolume /data/puppet
end-volume
volume files3
type protocol/client
option transport-type tcp
option remote-host files3.xx.com
option remote-subvolume /data/puppet
end-volume
volume replicate
type cluster/replicate
subvolumes files1 files2 files3
end-volume
volume writebehind
type performance/write-behind
option window-size 2MB
subvolumes replicate
end-volume
volume cache
type performance/io-cache
option cache-size 512MB
subvolumes writebehind
end-volume
root at puppet2:/home/supervisor#
Expected results:
root at puppet2:/home/supervisor# mount -t glusterfs /etc/gfs.vol /data2
root at puppet2:/home/supervisor#
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list