virsh 创建glusterfs池常见故障解析

问题１:
virsh # pool-start gv_KVM
error: Failed to start pool gv_KVM
error: internal error Child process (/bin/mount -t glusterfs 192.168.174.80:/gv_KVM -o direct-io-mode=1 /mnt/gv) unexpected exit status 32: mount: unknown filesystem type 'glusterfs'
解决方案:
安装glusterfs-fuse包.

问题２:
virsh # pool-start gv_KVM
error: Failed to start pool gv_KVM
error: internal error Child process (/bin/mount -t glusterfs 192.168.174.80:/gv_KVM -o direct-io-mode=1 /mnt/gv) unexpected exit status 1: Mount failed. Please check the log file for more details.


解决方案:

[2015-10-29 08:16:34.273043] E [client-handshake.c:1495:client_query_portmap_cbk] 0-gv_KVM-client-7: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
[2015-10-29 08:16:34.273090] I [client.c:2282:client_rpc_notify] 0-gv_KVM-client-7: disconnected from gv_KVM-client-7. Client process will keep trying to connect to glusterd until brick's port is available

极有可能新没有启用volume
[root@192_168_174_68 ~]# gluster
gluster> gluster volume status
unrecognized word: gluster (position 0)
gluster>  volume status       
Status of volume: gv0
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick 192.168.174.79:/opt/brick/gv0         49152     0          Y       23328
Brick 192.168.174.80:/opt/brick/gv0         49152     0          Y       26213
Brick 192.168.174.81:/opt/brick/gv0         49152     0          Y       13201
Brick 192.168.174.68:/opt/brick/gv0         49152     0          Y       14655
Brick 192.168.174.67:/opt/brick/gv0         49152     0          Y       29476
Brick 192.168.167.52:/opt/brick/gv0         49152     0          Y       19450
Brick 192.168.167.58:/opt/brick/gv0         49152     0          Y       6479
Brick 192.168.167.76:/opt/brick/gv0         49152     0          Y       21216
NFS Server on localhost                     N/A       N/A        N       N/A  
NFS Server on 192.168.174.81                N/A       N/A        N       N/A  
NFS Server on 192.168.167.58                2049      0          Y       27012
NFS Server on 192.168.174.67                N/A       N/A        N       N/A  
NFS Server on 192.168.174.80                N/A       N/A        N       N/A  
NFS Server on 192.168.167.52                2049      0          Y       4508
NFS Server on 192.168.174.79                N/A       N/A        N       N/A  
NFS Server on 192.168.167.76                N/A       N/A        N       N/A  
 
Task Status of Volume gv0
------------------------------------------------------------------------------
There are no active volume tasks
 
Volume gv_KVM is not started
 
Volume gv_kvm is not started
 
Status of volume: gv_zm
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick 192.168.174.68:/opt/brick/gv1         49153     0          Y       18878
Brick 192.168.174.67:/opt/brick/gv1         49153     0          Y       1019
NFS Server on localhost                     N/A       N/A        N       N/A  
NFS Server on 192.168.174.81                N/A       N/A        N       N/A  
NFS Server on 192.168.167.52                2049      0          Y       4508
NFS Server on 192.168.174.79                N/A       N/A        N       N/A  
NFS Server on 192.168.174.67                N/A       N/A        N       N/A  
NFS Server on 192.168.174.80                N/A       N/A        N       N/A  
NFS Server on 192.168.167.58                2049      0          Y       27012
NFS Server on 192.168.167.76                N/A       N/A        N       N/A  
 
Task Status of Volume gv_zm
------------------------------------------------------------------------------
There are no active volume tasks
 
gluster>

[root@192-168-167-76 peers]# gluster volume start gv_KVM
volume start: gv_KVM: success

virsh # pool-start gv_KVM
Pool gv_KVM started
启动成功
virsh #