[Gluster-devel] QEMU (and other libgfapi client?) crashes on add-brick / replace-brick
Guido De Rosa
guido.derosa at vemarsas.it
Thu Aug 29 15:27:08 UTC 2013
Sorry for the delayed response... Well, I've just done a git pull (master
branch, now @ 3a3441e) and apparently the fuse mount problem has been
solved (can't figure out which commit exactly did it).
Still not sure about the replace-brick + libgfapi thing. I will get you
updated, thanks for now.
Guido
2013/8/14 Anand Avati <anand.avati at gmail.com>
>
> On Wed, Jul 31, 2013 at 9:48 AM, Guido De Rosa <guido.derosa at vemarsas.it>wrote:
>
>> Well, there's another problem, possibly related, that I didn't notice:
>> I'm unable to mount!
>>
>> (Although libgfapi is meant to bypass fuse-mount, I've read that you need
>> FUSE working in the same machine where you issue a replace-brick command
>> [1])
>>
>> $ git clone ssh://guidoderosa@git.gluster.org/glusterfs
>>
>> (master branch @ a960f92)
>>
>> $ ./autogen.sh
>>
>> $ ./configure --enable-debug && make && sudo make install
>>
>> # /etc/init.d/glusterd start
>>
>> # gluster volume create gv transport tcp 192.168.232.179:
>> /var/export/gluster/gv
>> volume create: gv: success: please start the volume to access data
>>
>> # gluster volume start gv
>> volume start: gv: success
>>
>> And here the problem:
>>
>> # mount -t glusterfs localhost:/gv /mnt/gv
>> Mount failed. Please check the log file for more details.
>>
>>
> The log to check is /usr/local/var/log/glusterfs/mnt-gv.log
>
> Please check what the error was in that log.
>
> Avati
>
>
>
>
>> The same issue holds if I apply the patches you suggested, then clean
>> sources, rebuild & reinstall. (If there's some relation..,)
>>
>> $ git pull ssh://guidoderosa@git.gluster.org/glusterfs refs/changes/
>> 07/5407/2
>>
>> etc.
>>
>> Here are the relevant logs:
>>
>> /usr/local/var/log/glusterfs/bricks/var-export-gluster-gv.log:
>>
>> Final graph:
>>
>> +------------------------------------------------------------------------------+
>> 1: volume gv-posix
>> 2: type storage/posix
>> 3: option glusterd-uuid 42ff1e51-7c77-4c70-9e1b-3e6207935bee
>> 4: option directory /var/export/gluster/gv
>> 5: option volume-id a562cb7c-0edf-4efa-afc6-80ea4e3fe978
>> 6: end-volume
>> 7:
>> 8: volume gv-changelog
>> 9: type features/changelog
>> 10: option changelog-brick /var/export/gluster/gv
>> 11: option changelog-dir /var/export/gluster/gv/.glusterfs/changelogs
>> 12: subvolumes gv-posix
>> 13: end-volume
>> 14:
>> 15: volume gv-access-control
>> 16: type features/access-control
>> 17: subvolumes gv-changelog
>> 18: end-volume
>> 19:
>> 20: volume gv-locks
>> 21: type features/locks
>> 22: subvolumes gv-access-control
>> 23: end-volume
>> 24:
>> 25: volume gv-io-threads
>> 26: type performance/io-threads
>> 27: subvolumes gv-locks
>> 28: end-volume
>> 29:
>> 30: volume gv-index
>> 31: type features/index
>> 32: option index-base /var/export/gluster/gv/.glusterfs/indices
>> 33: subvolumes gv-io-threads
>> 34: end-volume
>> 35:
>> 36: volume gv-marker
>> 37: type features/marker
>> 38: option volume-uuid a562cb7c-0edf-4efa-afc6-80ea4e3fe978
>> 39: option timestamp-file /var/lib/glusterd/vols/gv/marker.tstamp
>> 40: option xtime off
>> 41: option quota off
>> 42: subvolumes gv-index
>> 43: end-volume
>> 44:
>> 45: volume /var/export/gluster/gv
>> 46: type debug/io-stats
>> 47: option latency-measurement off
>> 48: option count-fop-hits off
>> 49: subvolumes gv-marker
>> 50: end-volume
>> 51:
>> 52: volume gv-server
>> 53: type protocol/server
>> 54: option transport.socket.listen-port 49152
>> 55: option rpc-auth.auth-glusterfs on
>> 56: option rpc-auth.auth-unix on
>> 57: option rpc-auth.auth-null on
>> 58: option transport-type tcp
>> 59: option auth.login./var/export/gluster/gv.allow
>> ae4ffb2b-75fb-4b5a-b9d3-6c9e390fee03
>> 60: option auth.login.ae4ffb2b-75fb-4b5a-b9d3-6c9e390fee03.password
>> 041ee2e7-e8cf-4ecd-bba6-655348721610
>> 61: option auth.addr./var/export/gluster/gv.allow *
>> 62: subvolumes /var/export/gluster/gv
>> 63: end-volume
>> 64:
>>
>> /usr/local/var/log/glusterfs/usr-local-etc-glusterfs-glusterd.vol.log:
>>
>> Final graph:
>>
>> +------------------------------------------------------------------------------+
>> 1: volume management
>> 2: type mgmt/glusterd
>> 3: option rpc-auth.auth-glusterfs on
>> 4: option rpc-auth.auth-unix on
>> 5: option rpc-auth.auth-null on
>> 6: option transport.socket.listen-backlog 128
>> 7: option transport.socket.read-fail-log off
>> 8: option transport.socket.keepalive-interval 2
>> 9: option transport.socket.keepalive-time 10
>> 10: option transport-type rdma
>> 11: option working-directory /var/lib/glusterd
>> 12: end-volume
>> 13:
>>
>> +------------------------------------------------------------------------------+
>>
>> Thanks,
>>
>> Guido
>>
>> ---
>> [1] This is for older versions and I'm not sure the same holds for 3.4
>> http://www.gluster.org/wp-content/uploads/2012/05/Gluster_File_System-3.3.0-Administration_Guide-en-US.pdf Sec
>> 7.4
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20130829/5e2badf3/attachment-0001.html>
More information about the Gluster-devel
mailing list