[Bugs] [Bug 1272404] New: Data Tiering:error "[2015-10-14 18:15:09.270483] E [MSGID: 122037] [ec-common.c:1502:ec_update_size_version_done] 0-tiervolume-disperse-1: Failed to update version and size [Input/output error]"

[bugzilla at redhat.com]

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

            Bug ID: 1272404
           Summary: Data Tiering:error "[2015-10-14 18:15:09.270483] E
                    [MSGID: 122037]
                    [ec-common.c:1502:ec_update_size_version_done]
                    0-tiervolume-disperse-1: Failed to update version and
                    size [Input/output error]"
           Product: GlusterFS
           Version: 3.7.5
         Component: tiering
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
=========================
On the longevity/stress setup we are getting the error message 
[2015-10-14 18:15:09.270412] E [MSGID: 122034]
[ec-common.c:439:ec_child_select] 0-tiervolume-disperse-1: Insufficient
available childs for this request (have 1, need 6
)
[2015-10-14 18:15:09.270483] E [MSGID: 122037]
[ec-common.c:1502:ec_update_size_version_done] 0-tiervolume-disperse-1: Failed
to update version and size [Input/output e
rror]
[2015-10-14 18:15:10.873293] E [MSGID: 122034]
[ec-common.c:439:ec_child_select] 0-tiervolume-disperse-0: Insufficient
available childs for this request (have 1, need 6
)
[2015-10-14 18:15:10.873470] E [MSGID: 122037]
[ec-common.c:1502:ec_update_size_version_done] 0-tiervolume-disperse-0: Failed
to update version and size [Input/output e
rror]
[2015-10-14 18:15:10.875723] E [MSGID: 122034]
[ec-common.c:439:ec_child_select] 0-tiervolume-disperse-0: Insufficient
available childs for this request (have 1, need 6
)
[2015-10-14 18:15:10.875742] E [MSGID: 122037]
[ec-common.c:1502:ec_update_size_version_done] 0-tiervolume-disperse-0: Failed
to update version and size [Input/output e
rror]
[2015-10-14 18:15:10.876542] E [MSGID: 122034]
[ec-common.c:439:ec_child_select] 0-tiervolume-disperse-0: Insufficient
available childs for this request (have 1, need 6
)
[2015-10-14 18:15:10.876567] E [MSGID: 122037]
[ec-common.c:1502:ec_update_size_version_done] 0-tiervolume-disperse-0: Failed
to update version and size [Input/output e
rror]
[2015-10-14 18:15:10.882593] E [MSGID: 122034]
[ec-common.c:439:ec_child_select] 0-tiervolume-disperse-1: Insufficient
available childs for this request (have 1, need 6
)
[2015-10-14 18:15:10.882645] E [MSGID: 122037]
[ec-common.c:1502:ec_update_size_version_done] 0-tiervolume-disperse-1: Failed
to update version and size [Input/output e
rror]
[2015-10-14 18:15:10.885247] E [MSGID: 122034]
[ec-common.c:439:ec_child_select] 0-tiervolume-disperse-1: Insufficient
available childs for this request (have 1, need 6
)
[2015-10-14 18:15:10.885293] E [MSGID: 122037]
[ec-common.c:1502:ec_update_size_version_done] 0-tiervolume-disperse-1: Failed
to update version and size [Input/output e
rror]





Version-Release number of selected component (if applicable):
=============================================================

glusterfs-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64



Steps Carried:
==============

1. Created 12 node cluster
2. Create tiered volume with Hot tier as (6 x 2) and Cold tier as (2 x (6 + 2)
= 16)
3. Fuse Mount the volume on 3 clients RHEL7.2,RHEl7.1 and RHEL6.7
4. Start creating data from each client:

Client 1:
=========
[root at dj ~]# crefi --multi -n 10 -b 10 -d 10 --max=1024k --min=5k --random -T 5
-t text -I 5 --fop=create /mnt/fuse/

Client 2:
=========
[root at mia ~]# cd /mnt/fuse/
[root at mia fuse]# for i in {1..10}; do cp -rf /etc etc.$i ; sleep 100 ; done

Client 3:
=========
[root at wingo fuse]# for i in {1..999}; do dd if=/dev/zero of=dd.$i bs=1M count=1
; sleep 10 ; done

5. After a while, the data creation of client 1 and client 2 should be
completed while the data creation from client 3 will still be inprogress

6. At this point the data creation will be of only 1 file from client 3 in
every 10 sec.

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