[Bugs] [Bug 1664215] Toggling readdir-ahead translator off causes some clients to umount some of its volumes

bugzilla at redhat.com bugzilla at redhat.com
Wed Jan 9 04:47:36 UTC 2019


https://bugzilla.redhat.com/show_bug.cgi?id=1664215

Amar Tumballi <atumball at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|unspecified                 |high
           Assignee|atumball at redhat.com         |rgowdapp at redhat.com



--- Comment #3 from Amar Tumballi <atumball at redhat.com> ---
> [2019-01-04 04:55:51.453074] I [fuse-bridge.c:4835:fuse_graph_sync] 0-fuse: switched to graph 4

Notice the graph number is 4 here.

> [2019-01-04 04:55:51.454990] I [MSGID: 114021] [client.c:2369:notify] 2-el_data-client-0: current graph is no longer active, destroying rpc_client
> [2019-01-04 04:55:51.455028] I [MSGID: 114021] [client.c:2369:notify] 2-el_data-client-1: current graph is no longer active, destroying rpc_client
> [2019-01-04 04:55:51.455037] I [MSGID: 114018] [client.c:2285:client_rpc_notify] 2-el_data-client-0: disconnected from el_data-client-0. Client process will keep trying to connect to glusterd until brick's port is available
> [2019-01-04 04:55:51.455080] I [MSGID: 114018] [client.c:2285:client_rpc_notify] 2-el_data-client-1: disconnected from el_data-client-1. Client process will keep trying to connect to glusterd until brick's port is available

All the above logs are from graph 2, (2-el_data-client-0 signifies, in graph 2,
volume name el_data, and client-0 is protocol/client translator). So this is
expected.

I don't think this is the reason for the umount. These logs can turn up in any
such graph change options (like write-behind on/off, read-ahead on/off, etc).
Not sure if this is enough to debug this umount issues.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Bugs mailing list