[Bugs] [Bug 1416251] [SNAPSHOT] With all USS plugin enable .snaps directory is not visible in cifs mount as well as windows mount

[bugzilla at redhat.com]

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



--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
Description of problem:
.snaps directory is not visible in cifs mount as well as windows smb mount,
even after enabling USS & VSS plugins.

Over fuse mount the .snaps directory is seen and is accessible also.

Currently this issue is seen in a SSL enabled cluster and another cluster setup
over EC volume where there is no SSL setup.

The below mentioned information is grabbed from the setup where there is a EC
volume.

Disconnect messages are seen in the client logs

[2017-01-09 09:32:57.751250] E [socket.c:2309:socket_connect_finish]
0-test-ec-snapd-client: connection to ::1:49158 failed (Connection refused)

[2017-01-09 09:32:57.751291] T [socket.c:721:__socket_disconnect]
0-test-ec-snapd-client: disconnecting 0x7fbf60061810, state=2 gen=0 sock=53


Version-Release number of selected component (if applicable):
samba-client-libs-4.4.6-4.el7rhgs.x86_64
glusterfs-client-xlators-3.8.4-11.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Over an EC volume 2(4+2) enable USS & show-snapshot-directory
2. Enable all VSS plugin
3. Take a snapshot
4. Activate the snapshot
5. Do a cifs mount and also mount the volume over a windows client machine (say
windows10)
6. Check for the .snaps directory in cifs mount as well as windows mount

Actual results:
.snaps directory is not seen or accessible or present

Expected results:
.snaps directory should be present

Additional info:

[2017-01-09 09:32:57.751250] E [socket.c:2309:socket_connect_finish]
0-test-ec-snapd-client: connection to ::1:49158 failed (Connection refused)
[2017-01-09 09:32:57.751291] T [socket.c:721:__socket_disconnect]
0-test-ec-snapd-client: disconnecting 0x7fbf60061810, state=2 gen=0 sock=53
[2017-01-09 09:32:57.751312] D [socket.c:683:__socket_shutdown]
0-test-ec-snapd-client: shutdown() returned -1. Transport endpoint is not
connected
[2017-01-09 09:32:57.751327] D [socket.c:728:__socket_disconnect]
0-test-ec-snapd-client: __socket_teardown_connection () failed: Transport
endpoint is not connected

[2017-01-09 09:32:57.751340] D [socket.c:2403:socket_event_handler]
0-transport: disconnecting now

[2017-01-09 09:32:57.752014] D
[rpc-clnt-ping.c:93:rpc_clnt_remove_ping_timer_locked] (-->
/lib64/libglusterfs.so.0(_gf_log_callingfn+0x192)[0x7fbf73b1b602] (-->
/lib64/libgfrpc.so.0(rpc_clnt_remove_ping_timer_locked+0x8e)[0x7fbf74011b9e]
(--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x5b)[0x7fbf7400dfbb]
(--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x94)[0x7fbf7400e874] (-->
/lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fbf7400a893] ))))) 0-:
::1:49158: ping timer event already removed

[2017-01-09 09:32:57.752064] D [MSGID: 0] [client.c:2264:client_rpc_notify]
0-test-ec-snapd-client: got RPC_CLNT_DISCONNECT

[2017-01-09 09:32:57.752095] D [MSGID: 0]
[event-epoll.c:587:event_dispatch_epoll_handler] 0-epoll: generation bumped on
idx=13 from gen=2764 to slot->gen=2765, fd=53, slot->fd=53

[2017-01-09 09:33:01.733914] T [rpc-clnt.c:422:rpc_clnt_reconnect]
0-test-ec-snapd-client: attempting reconnect

[2017-01-09 09:33:01.733992] T [socket.c:2991:socket_connect]
0-test-ec-snapd-client: connecting 0x7fbf60061810, state=2 gen=0 sock=-1

[2017-01-09 09:33:01.734016] D [name.c:168:client_fill_address_family]
0-test-ec-snapd-client: address-family not specified, marking it as unspec for
getaddrinfo to resolve from (remote-host: localhost)

[2017-01-09 09:33:01.734032] T [name.c:238:af_inet_client_get_remote_sockaddr]
0-test-ec-snapd-client: option remote-port missing in volume
test-ec-snapd-client. Defaulting to 24007

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