[Gluster-users] GlusterFS 3.6.2: Can't mount GlusterFS volume

Andreas Hollaus Andreas.Hollaus at ericsson.com
Mon Jun 22 07:35:28 UTC 2015


Hi,

I can't mount the GlusterFS volume anymore. Any ideas what could be wrong? I guess
the volume should mount even though the remote brick might not be available? In this
case it is available ('pingable'), but in some cases it may not be, which seems
pretty normal for a replicated volume.

Regards
Andreas

# mount -t glusterfs  10.32.0.48:c_glstr /mnt/c
Mount failed. Please check the log file for more details.

# ifconfig
.
.
.
efd       Link encap:Ethernet  HWaddr 02:00:00:03:00:00 
          inet addr:10.32.0.48  Bcast:10.32.255.255  Mask:255.255.0.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1476  Metric:1
          RX packets:743924 errors:0 dropped:0 overruns:0 frame:0
          TX packets:780286 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:37856125 (36.1 MiB)  TX bytes:87978721 (83.9 MiB)
.
.
.

# gluster volume status
Status of volume: c_glstr
Gluster process                        Port    Online    Pid
------------------------------------------------------------------------------
Brick 10.32.0.48:/opt/lvmdir/c2/brick            N/A    N    N/A
Brick 10.32.0.64:/opt/lvmdir/c2/brick            N/A    N    N/A
NFS Server on localhost                    N/A    N    N/A
Self-heal Daemon on localhost                N/A    Y    19708
NFS Server on 10.32.0.64                N/A    N    N/A
Self-heal Daemon on 10.32.0.64                N/A    Y    3050
 
Task Status of Volume c_glstr
------------------------------------------------------------------------------
There are no active volume tasks
 
# gluster volume info 
 
Volume Name: c_glstr
Type: Replicate
Volume ID: e052572c-c7ad-4d66-986f-621fbc48999e
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.32.0.48:/opt/lvmdir/c2/brick
Brick2: 10.32.0.64:/opt/lvmdir/c2/brick
Options Reconfigured:
network.ping-timeout: 4

# tail -100 /var/log/glusterfs/mnt-c.log
[2015-06-22 07:11:27.623703] W [fuse-bridge.c:779:fuse_attr_cbk] 0-glusterfs-fuse: 2:
LOOKUP() / => -1 (Transport endpoint is not connected)
[2015-06-22 07:11:27.627369] I [afr-common.c:3722:afr_local_init]
0-c_glstr-replicate-0: no subvolumes up
[2015-06-22 07:11:27.629200] I [fuse-bridge.c:4921:fuse_thread_proc] 0-fuse:
unmounting /mnt/c
[2015-06-22 07:11:27.629383] W [glusterfsd.c:1194:cleanup_and_exit] (--> 0-: received
signum (15), shutting down
[2015-06-22 07:11:27.629426] I [fuse-bridge.c:5599:fini] 0-fuse: Unmounting '/mnt/c'.
[2015-06-22 07:12:16.363797] I [MSGID: 100030] [glusterfsd.c:2018:main]
0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.6.2 (args:
/usr/sbin/glusterfs --volfile-server=10.32.0.48 --volfile-id=c_glstr /mnt/c)
[2015-06-22 07:12:16.379745] I [dht-shared.c:337:dht_init_regex] 0-c_glstr-dht: using
regex rsync-hash-regex = ^\.(.+)\.[^.]+$
[2015-06-22 07:12:16.384943] I [client.c:2280:notify] 0-c_glstr-client-0: parent
translators are ready, attempting connect on transport
[2015-06-22 07:12:16.385805] I [client.c:2280:notify] 0-c_glstr-client-1: parent
translators are ready, attempting connect on transport
Final graph:
+------------------------------------------------------------------------------+
  1: volume c_glstr-client-0
  2:     type protocol/client
  3:     option ping-timeout 4
  4:     option remote-host 10.32.0.48
  5:     option remote-subvolume /opt/lvmdir/c2/brick
  6:     option transport-type socket
  7:     option username b860abc7-dfeb-402c-baf3-ef13f1c3bb52
  8:     option password db5d45c9-58f7-49ad-8080-9197eb69695e
  9:     option send-gids true
 10: end-volume
 11: 
 12: volume c_glstr-client-1
 13:     type protocol/client
 14:     option ping-timeout 4
 15:     option remote-host 10.32.0.64
 16:     option remote-subvolume /opt/lvmdir/c2/brick
 17:     option transport-type socket
 18:     option username b860abc7-dfeb-402c-baf3-ef13f1c3bb52
 19:     option password db5d45c9-58f7-49ad-8080-9197eb69695e
 20:     option send-gids true
 21: end-volume
 22: 
 23: volume c_glstr-replicate-0
 24:     type cluster/replicate
 25:     subvolumes c_glstr-client-0 c_glstr-client-1
 26: end-volume
 27: 
 28: volume c_glstr-dht
 29:     type cluster/distribute
 30:     subvolumes c_glstr-replicate-0
 31: end-volume
 32: 
 33: volume c_glstr-write-behind
 34:     type performance/write-behind
 35:     subvolumes c_glstr-dht
 36: end-volume
 37: 
 38: volume c_glstr-read-ahead
 39:     type performance/read-ahead
 40:     subvolumes c_glstr-write-behind
 41: end-volume
 42: 
 43: volume c_glstr-io-cache
 44:     type performance/io-cache
 45:     subvolumes c_glstr-read-ahead
 46: end-volume
 47: 
 48: volume c_glstr-quick-read
 49:     type performance/quick-read
 50:     subvolumes c_glstr-io-cache
 51: end-volume
 52: 
 53: volume c_glstr-open-behind
 54:     type performance/open-behind
 55:     subvolumes c_glstr-quick-read
 56: end-volume
 57: 
 58: volume c_glstr-md-cache
 59:     type performance/md-cache
 60:     subvolumes c_glstr-open-behind
 61: end-volume
 62: 
 63: volume c_glstr
 64:     type debug/io-stats
 65:     option latency-measurement off
 66:     option count-fop-hits off
 67:     subvolumes c_glstr-md-cache
 68: end-volume
 69: 
 70: volume meta-autoload
 71:     type meta
 72:     subvolumes c_glstr
 73: end-volume
 74: 
+------------------------------------------------------------------------------+
[2015-06-22 07:12:16.387498] E [client-handshake.c:1496:client_query_portmap_cbk]
0-c_glstr-client-0: failed to get the port number for remote subvolume. Please run
'gluster volume status' on server to see if brick process is running.
[2015-06-22 07:12:16.387580] I [client.c:2215:client_rpc_notify] 0-c_glstr-client-0:
disconnected from c_glstr-client-0. Client process will keep trying to connect to
glusterd until brick's port is available
[2015-06-22 07:12:16.388006] E [client-handshake.c:1496:client_query_portmap_cbk]
0-c_glstr-client-1: failed to get the port number for remote subvolume. Please run
'gluster volume status' on server to see if brick process is running.
[2015-06-22 07:12:16.388079] I [client.c:2215:client_rpc_notify] 0-c_glstr-client-1:
disconnected from c_glstr-client-1. Client process will keep trying to connect to
glusterd until brick's port is available
[2015-06-22 07:12:16.388107] E [MSGID: 108006] [afr-common.c:3591:afr_notify]
0-c_glstr-replicate-0: All subvolumes are down. Going offline until atleast one of
them comes back up.
[2015-06-22 07:12:16.396709] I [fuse-bridge.c:5080:fuse_graph_setup] 0-fuse: switched
to graph 0
[2015-06-22 07:12:16.397056] I [fuse-bridge.c:4009:fuse_init] 0-glusterfs-fuse: FUSE
inited with protocol versions: glusterfs 7.22 kernel 7.22
[2015-06-22 07:12:16.397282] I [afr-common.c:3722:afr_local_init]
0-c_glstr-replicate-0: no subvolumes up
[2015-06-22 07:12:16.397660] I [afr-common.c:3722:afr_local_init]
0-c_glstr-replicate-0: no subvolumes up
[2015-06-22 07:12:16.397720] W [fuse-bridge.c:779:fuse_attr_cbk] 0-glusterfs-fuse: 2:
LOOKUP() / => -1 (Transport endpoint is not connected)
[2015-06-22 07:12:16.401992] I [afr-common.c:3722:afr_local_init]
0-c_glstr-replicate-0: no subvolumes up
[2015-06-22 07:12:16.403970] I [fuse-bridge.c:4921:fuse_thread_proc] 0-fuse:
unmounting /mnt/c
[2015-06-22 07:12:16.404133] W [glusterfsd.c:1194:cleanup_and_exit] (--> 0-: received
signum (15), shutting down
[2015-06-22 07:12:16.404159] I [fuse-bridge.c:5599:fini] 0-fuse: Unmounting '/mnt/c'.




More information about the Gluster-users mailing list