Bug 763010 (GLUSTER-1278)

Summary: bypassing translators didn't show warning message
Product: [Community] GlusterFS Reporter: Lakshmipathi G <lakshmipathi>
Component: io-cacheAssignee: Raghavendra G <raghavendra>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 3.1-alphaCC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTP Mount Type: ---
Documentation: DNR CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lakshmipathi G 2010-08-04 06:31:04 UTC
Reported in user-mailing list - 
http://gluster.org/pipermail/gluster-users/2010-August/005136.html

iocache didn't produce dangling warning message,when it's bypassed by trace translator.
------------------------
volume server01
    type protocol/client
    option transport-type tcp
    option remote-host server01
    option transport.socket.nodelay on
    option transport.remote-port 6996
    option remote-subvolume brick1
    option transport-timeout 10
end-volume

volume server02
    type protocol/client
    option transport-type tcp
    option remote-host server02
    option transport.socket.nodelay on
    option transport.remote-port 6996
    option remote-subvolume brick1
    option transport-timeout 10
end-volume

volume mirror-0
    type cluster/replicate
    subvolumes server01 server02
end-volume

volume writebehind
    type performance/write-behind
    option aggregate-size 32MB
    option cache-size 64MB
    subvolumes mirror-0
end-volume

volume iocache
    type performance/io-cache
    option cache-size 64MB
    subvolumes writebehind
end-volume

volume trace
    type debug/trace
    subvolumes server01-1
end-volume

Comment 1 Raghavendra G 2010-11-10 07:19:03 UTC
Configuration was wrong. trace had server01-1 as its child which was not defined. Once corrected, log file had dangling volume warnings.

[2010-11-10 15:55:04.726262] W [trace.c:2110:init] trace: dangling volume. check volfile 
[2010-11-10 15:55:04.726352] W [dict.c:1204:data_to_str] dict: @data=(nil)
[2010-11-10 15:55:04.726380] W [dict.c:1204:data_to_str] dict: @data=(nil)
[2010-11-10 15:55:04.726411] W [io-cache.c:1834:init] iocache: dangling volume. check volfile 
[2010-11-10 15:55:04.726437] W [dict.c:1204:data_to_str] dict: @data=(nil)
[2010-11-10 15:55:04.726480] W [dict.c:1204:data_to_str] dict: @data=(nil)
[2010-11-10 15:55:04.729453] W [rpc-transport.c:566:validate_volume_options] server02: option 'transport.remote-por
t' is deprecated, preferred is 'remote-port', continuing with correction
[2010-11-10 15:55:05.333753] W [rpc-transport.c:566:validate_volume_options] server01: option 'transport.remote-por
t' is deprecated, preferred is 'remote-port', continuing with correction
[2010-11-10 15:55:05.962523] W [graph.c:120:_log_if_option_is_invalid] writebehind: option 'aggregate-size' is not 
recognized
[2010-11-10 15:55:05.962588] W [graph.c:120:_log_if_option_is_invalid] server02: option 'transport-timeout' is not 
recognized
[2010-11-10 15:55:05.962616] W [graph.c:120:_log_if_option_is_invalid] server02: option 'remote-port' is not recogn
ized
[2010-11-10 15:55:05.962640] W [graph.c:120:_log_if_option_is_invalid] server02: option 'transport.socket.nodelay' 
is not recognized
[2010-11-10 15:55:05.962667] W [graph.c:120:_log_if_option_is_invalid] server01: option 'transport-timeout' is not 
recognized
[2010-11-10 15:55:05.962691] W [graph.c:120:_log_if_option_is_invalid] server01: option 'remote-port' is not recogn
ized
[2010-11-10 15:55:05.962714] W [graph.c:120:_log_if_option_is_invalid] server01: option 'transport.socket.nodelay' 
is not recognized
Given volfile:
+------------------------------------------------------------------------------+
  1: volume server01
  2:     type protocol/client
  3:     option transport-type tcp
  4:     option remote-host server01
  5:     option transport.socket.nodelay on
  6:     option transport.remote-port 6996
  7:     option remote-subvolume brick1
  8:     option transport-timeout 10
  9: end-volume
 10: 
 11: volume server02
 12:     type protocol/client
 13:     option transport-type tcp
 14:     option remote-host server02
 15:     option transport.socket.nodelay on
 16:     option transport.remote-port 6996
 17:     option remote-subvolume brick1
 18:     option transport-timeout 10
 19: end-volume
 20: 
 21: volume mirror-0
 22:     type cluster/replicate
 23:     subvolumes server01 server02
 24: end-volume
 25: 
 26: volume writebehind
 27:     type performance/write-behind
 28:     option aggregate-size 32MB
 29:     option cache-size 64MB
 30:     subvolumes mirror-0
 31: end-volume
 32: 
 33: volume iocache
 34:     type performance/io-cache
 35:     option cache-size 64MB
 36:     subvolumes writebehind
 37: end-volume
 38: 
 39: volume trace
 40:     type debug/trace
 41:     subvolumes server01
 42: end-volume
+------------------------------------------------------------------------------+
[2010-11-10 15:55:05.962890] E [socket.c:1657:socket_connect_finish] server02: connection to  failed (Connection re
fused)
[2010-11-10 15:55:05.962937] E [afr-common.c:2598:afr_notify] mirror-0: All subvolumes are down. Going offline unti
l atleast one of them comes back up.
[2010-11-10 15:55:05.962999] E [afr-common.c:2598:afr_notify] mirror-0: All subvolumes are down. Going offline unti
l atleast one of them comes back up.
[2010-11-10 15:55:06.255514] E [socket.c:1657:socket_connect_finish] server01: connection to  failed (Connection re
fused)