Description of problem: while I/O is happening on the mount point keep on add-brick for a stripe volume then I/O fails at some point in time Version-Release number of selected component (if applicable): Mainline How reproducible: often Steps to Reproduce: 1.create a stripe volume with count 2 2.mount the volume and start kernel untar on the mount point 3.keep on adding bricks to the volume i.e. volume becomes distributed-stripe with increasing distribute count Actual results: I/O fails Expected results: untar should succeed Additional info: This test passes on distributed-stripe without brick count change, passed on plain stripe , passed on plain distribute. LOG ==== [2012-02-21 00:10:27.702464] I [client-handshake.c:923:client_setvolume_cbk] 3-strvol-client-9: Connected to 10.1.11.118:24049, attached to remote volume '/br/st10'. [2012-02-21 00:10:27.706431] I [fuse-bridge.c:3699:fuse_graph_setup] 0-fuse: switched to graph 3 [2012-02-21 00:10:28.601401] E [stripe.c:137:stripe_ctx_handle] 3-strvol-stripe-1: Failed to get stripe-size [2012-02-21 00:10:28.880476] E [stripe.c:487:stripe_lookup_cbk] 3-strvol-stripe-1: Error getting fctx info from dict [2012-02-21 00:10:28.880552] E [stripe.c:137:stripe_ctx_handle] 3-strvol-stripe-1: Failed to get stripe-size [2012-02-21 00:10:28.880585] E [stripe.c:487:stripe_lookup_cbk] 3-strvol-stripe-1: Error getting fctx info from dict [2012-02-21 00:16:48.568906] E [stripe.c:137:stripe_ctx_handle] 3-strvol-stripe-0: Failed to get stripe-size [2012-02-21 00:16:48.576113] E [stripe.c:487:stripe_lookup_cbk] 3-strvol-stripe-0: Error getting fctx info from dict [2012-02-21 00:16:48.576170] E [stripe.c:137:stripe_ctx_handle] 3-strvol-stripe-0: Failed to get stripe-size [2012-02-21 00:16:48.576191] E [stripe.c:487:stripe_lookup_cbk] 3-strvol-stripe-0: Error getting fctx info from dict
The issue is seen when a non-distribute volume is converted to a distribute volume(through add-brick). Existing directories would not have any extended attributes set on them, which would lead to failure. Removing the 3.3.0beta milestone, as this issue can not be fixed in this time frame. *** This bug has been marked as a duplicate of bug 815227 ***