[Bugs] [Bug 1221964] New: After adding brick not able to see the content of the mount and getting "cannot open directory .: Structure needs cleaning"

bugzilla at redhat.com bugzilla at redhat.com
Fri May 15 10:54:05 UTC 2015


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

            Bug ID: 1221964
           Summary: After adding brick not able to see the content of the
                    mount and getting "cannot open directory .: Structure
                    needs cleaning"
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: rmekala at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
===========================
After adding brick not able to see the content of the mount and getting "cannot
open directory .: Structure needs cleaning"


Version-Release number of selected component (if applicable):
===============================
glusterfs-server-3.7.0-2.el6rhs.x86_64


How reproducible:


Steps to Reproduce:
==========================
1.Create distributed volume with two bricks and mount it on client (FUSE mount)
2.Create files on mount using DD at that time add new more brick to the volume
3.After that ls giving follwoing messages 

"cannot open directory .: Structure needs cleaning"

snippet of the log
=======================

34: volume vol2-readdir-ahead
 35:     type performance/readdir-ahead
 36:     subvolumes vol2-read-ahead
 37: end-volume
 38:
 39: volume vol2-io-cache
 40:     type performance/io-cache
 41:     subvolumes vol2-readdir-ahead
 42: end-volume
 43:
 44: volume vol2-quick-read
 45:     type performance/quick-read
 46:     subvolumes vol2-io-cache
 47: end-volume
 48:
 49: volume vol2-open-behind
 50:     type performance/open-behind
 51:     subvolumes vol2-quick-read
 52: end-volume
 53:
 54: volume vol2-md-cache
 55:     type performance/md-cache
 56:     subvolumes vol2-open-behind
 57: end-volume
 58:
 59: volume vol2
 60:     type debug/io-stats
 61:     option latency-measurement off
 62:     option count-fop-hits off
 63:     subvolumes vol2-md-cache
 64: end-volume
 65:
 66: volume meta-autoload
 67:     type meta
 68:     subvolumes vol2
 69: end-volume
 70:
+------------------------------------------------------------------------------+
[2015-05-15 09:56:16.566071] I [rpc-clnt.c:1807:rpc_clnt_reconfig]
0-vol2-client-2: changing port to 49177 (from 0)
[2015-05-15 09:56:16.569811] I
[client-handshake.c:1405:select_server_supported_programs] 0-vol2-client-1:
Using Program GlusterFS 3.3, Num (1298437), Version (330)
[2015-05-15 09:56:16.570256] I [client-handshake.c:1193:client_setvolume_cbk]
0-vol2-client-1: Connected to vol2-client-1, attached to remote volume
'/rajesh3/brick9'.
[2015-05-15 09:56:16.570272] I [client-handshake.c:1203:client_setvolume_cbk]
0-vol2-client-1: Server and Client lk-version numbers are not same, reopening
the fds
[2015-05-15 09:56:16.570641] I
[client-handshake.c:187:client_set_lk_version_cbk] 0-vol2-client-1: Server lk
version = 1
[2015-05-15 09:56:16.571987] I
[client-handshake.c:1405:select_server_supported_programs] 0-vol2-client-2:
Using Program GlusterFS 3.3, Num (1298437), Version (330)
[2015-05-15 09:56:16.572515] I [client-handshake.c:1193:client_setvolume_cbk]
0-vol2-client-2: Connected to vol2-client-2, attached to remote volume
'/rajesh3/brick9'.
[2015-05-15 09:56:16.572540] I [client-handshake.c:1203:client_setvolume_cbk]
0-vol2-client-2: Server and Client lk-version numbers are not same, reopening
the fds
[2015-05-15 09:56:16.577077] I [fuse-bridge.c:5077:fuse_graph_setup] 0-fuse:
switched to graph 0
[2015-05-15 09:56:16.577188] I
[client-handshake.c:187:client_set_lk_version_cbk] 0-vol2-client-2: Server lk
version = 1
[2015-05-15 09:56:16.577331] I [fuse-bridge.c:4007:fuse_init] 0-glusterfs-fuse:
FUSE inited with protocol versions: glusterfs 7.22 kernel 7.14
[2015-05-15 09:56:16.578792] E [MSGID: 109014]
[dht-layout.c:312:dht_disk_layout_merge] 0-vol2-dht: Invalid disk layout:
Invalid count -1431432340
[2015-05-15 09:56:16.578825] W [MSGID: 109017]
[dht-layout.c:397:dht_layout_merge] 0-vol2-dht: layout merge from subvolume
vol2-client-2 failed
[2015-05-15 09:56:16.578865] W [MSGID: 109005]
[dht-selfheal.c:1785:dht_selfheal_directory] 0-vol2-dht: Directory selfheal
failed: Unable to form layout for directory /
[2015-05-15 09:56:16.580651] W [fuse-bridge.c:780:fuse_attr_cbk]
0-glusterfs-fuse: 2: LOOKUP() / => -1 (Structure needs cleaning)
[2015-05-15 09:56:16.588306] I [fuse-bridge.c:4924:fuse_thread_proc] 0-fuse:
unmounting /mnt/vol2
[2015-05-15 09:56:16.580514] E [MSGID: 109014]
[dht-layout.c:312:dht_disk_layout_merge] 0-vol2-dht: Invalid disk layout:
Invalid count -1431432340
[2015-05-15 09:56:16.580516] W [MSGID: 109017]
[dht-layout.c:397:dht_layout_merge] 0-vol2-dht: layout merge from subvolume
vol2-client-2 failed
[2015-05-15 09:56:16.580529] W [MSGID: 109005]
[dht-selfheal.c:1785:dht_selfheal_directory] 0-vol2-dht: Directory selfheal
failed: Unable to form layout for directory /
[2015-05-15 09:56:16.588712] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-:
received signum (15), shutting down
[2015-05-15 09:56:16.588740] I [fuse-bridge.c:5619:fini] 0-fuse: Unmounting
'/mnt/vol2'.


Actual results:
====================
Even After adding the bricks to new volume, User should be able view the
content of the mount

Expected results:



Additional info:

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


More information about the Bugs mailing list