[Gluster-users] Possible error not being returned
Xavier Hernandez
xhernandez at datalab.es
Mon May 23 07:21:47 UTC 2016
It's possible that the operation that failed is an internal one made by
disperse itself or any other translator, so this error is not reported
to the application.
The read issued by the application will only fail if anything fails
while processing the read itself. If everything goes well, the read will
succeed and it should contain healthy data.
What configuration are you using ? (gluster volume info)
What are you doing exactly ? (workload)
Why is one brick down/damaged ? are you doing tests ? how are you doing
them ?
Best regards,
Xavi
On 20/05/16 16:54, Ankireddypalle Reddy wrote:
> Hi,
>
> Did anyone get a chance to check this. We are intermittently
> receiving corrupted data in read operations because of this.
>
>
>
> Thanks and Regards,
>
> Ram
>
>
>
> *From:*gluster-users-bounces at gluster.org
> [mailto:gluster-users-bounces at gluster.org] *On Behalf Of *Ankireddypalle
> Reddy
> *Sent:* Thursday, May 19, 2016 3:59 PM
> *To:* gluster-users at gluster.org
> *Subject:* [Gluster-users] Possible error not being returned
>
>
>
> Hi,
>
> A disperse volume was configured on servers with limited
> network bandwidth. Some of the read operations failed with error
>
>
>
> [2016-05-16 18:38:36.035559] E [MSGID: 122034]
> [ec-common.c:461:ec_child_select] 0-SDSStoragePool-disperse-2:
> Insufficient available childs for this request (have 1, need 2)
>
> [2016-05-16 18:38:36.035713] W [fuse-bridge.c:2213:fuse_readv_cbk]
> 0-glusterfs-fuse: 155121179: READ => -1 (Input/output error)
>
>
>
> For some read operations just the following error was logged but the I/O
> did not fail.
>
> [2016-05-16 18:42:45.401570] E [MSGID: 122034]
> [ec-common.c:461:ec_child_select] 0-SDSStoragePool-disperse-3:
> Insufficient available childs for this request (have 1, need 2)
>
> [2016-05-16 18:42:45.402054] W [MSGID: 122053]
> [ec-common.c:116:ec_check_status] 0-SDSStoragePool-disperse-3: Operation
> failed on some subvolumes (up=7, mask=6, remaining=0, good=6, bad=1)
>
>
>
> We are receiving corrupted data in the read operation when the error is
> logged but the read call did not return any error.
>
>
>
> Thanks and Regards,
>
> Ram
>
>
>
>
>
>
>
>
>
> ***************************Legal Disclaimer***************************
>
> "This communication may contain confidential and privileged material for the
>
> sole use of the intended recipient. Any unauthorized review, use or distribution
>
> by others is strictly prohibited. If you have received the message by mistake,
>
> please advise the sender by reply email and delete the message. Thank you."
>
> **********************************************************************
>
>
> ***************************Legal Disclaimer***************************
> "This communication may contain confidential and privileged material for the
> sole use of the intended recipient. Any unauthorized review, use or distribution
> by others is strictly prohibited. If you have received the message by mistake,
> please advise the sender by reply email and delete the message. Thank you."
> **********************************************************************
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>
More information about the Gluster-users
mailing list