[Gluster-devel] NetBSD regression status upate

[Emmanuel Dreyfus]

Atin Mukherjee <amukherj at redhat.com> wrote:

> Please look at glusterd_stop_volume () in
> xlators/mgmt/glusterd/src/glusterd-volume-ops.c

I see oomeone thought it was a good idea to duplicate GLUSTERFS_GET_AUX_MOUNT_PIDFILE in  cli/src/cli.h and xlators/mgmt/glusterd/src/glusterd.h...

In this problem, the gluterfs process responsible for the offending 
mount does not manage to exit. It loops forever. The logs are below.
Is this another incarnation of Pranith's second case?

[2015-05-08 07:02:54.469754] I [ec.c:273:ec_down] 0-patchy-disperse-0: Going DOWN
[2015-05-08 07:02:54.772678] E [ec-common.c:1380:ec_update_size_version_done] 0-patchy-disperse-0: Failed to update version and size (error 57)
[2015-05-08 07:02:54.772845] W [ec-common.c:1325:ec_unlocked] 0-patchy-disperse-0: entry/inode unlocking failed (GETXATTR)
[2015-05-08 07:02:54.773558] W [fuse-bridge.c:780:fuse_attr_cbk] 0-glusterfs-fuse: 79: LOOKUP() / => -1 (Socket is not connected)
[2015-05-08 07:02:54.784076] W [socket.c:642:__socket_rwv] 0-patchy-client-2: readv on 23.253.160.60:49154 failed (No message available)
[2015-05-08 07:02:54.784203] I [client.c:2086:client_rpc_notify] 0-patchy-client-2: disconnected from patchy-client-2. Client process will keep trying to connect to glusterd until brick's port is available
[2015-05-08 07:02:57.849678] W [fuse-bridge.c:3015:fuse_statfs_cbk] 0-glusterfs-fuse: 82: ERR => -1 (Socket is not connected)

(repeated)

[2015-05-08 07:03:03.045068] W [fuse-bridge.c:3015:fuse_statfs_cbk] 0-glusterfs-fuse: 87: ERR => -1 (Socket is not connected)
[2015-05-08 07:03:04.083091] W [fuse-bridge.c:3015:fuse_statfs_cbk] 0-glusterfs-fuse: 88: ERR => -1 (Socket is not connected)
[2015-05-08 07:03:04.873832] E [client-handshake.c:1488:client_query_portmap_cbk] 0-patchy-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-05-08 07:03:04.873969] I [client.c:2086:client_rpc_notify] 0-patchy-client-0: disconnected from patchy-client-0. Client process will keep trying to connect to glusterd until brick's port is available
[2015-05-08 07:03:04.874066] E [client-handshake.c:1488:client_query_portmap_cbk] 0-patchy-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-05-08 07:03:04.874151] E [client-handshake.c:1488:client_query_portmap_cbk] 0-patchy-client-2: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.
[2015-05-08 07:03:04.874271] I [client.c:2086:client_rpc_notify] 0-patchy-client-2: disconnected from patchy-client-2. Client process will keep trying to connect to glusterd until brick's port is available
[2015-05-08 07:03:04.874439] I [client.c:2086:client_rpc_notify] 0-patchy-client-1: disconnected from patchy-client-1. Client process will keep trying to connect to glusterd until brick's port is available
[2015-05-08 07:03:05.124826] W [fuse-bridge.c:3015:fuse_statfs_cbk] 0-glusterfs-fuse: 89: ERR => -1 (Socket is not connected)
[2015-05-08 07:03:06.167065] W [fuse-bridge.c:3015:fuse_statfs_cbk] 0-glusterfs-fuse: 90: ERR => -1 (Socket is not connected)

(repeated)


-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org