[Gluster-users] Cascading errors and very bad write performance

[Geoffrey Letessier]

For additional information, if I [re]set the brick-log-level volume parameter to INFO, where what i can notice (thousands of thousands…) in my brick logs when I’m writing something:
[2015-08-06 23:44:22.805293] W [marker-quota.c:3379:_mq_initiate_quota_txn] 0-vol_home-marker: parent is NULL for <gfid:621f5366-18fa-4d46-8796-4532643d94cd>, aborting updation txn
[2015-08-06 23:44:22.805772] W [marker-quota.c:3379:_mq_initiate_quota_txn] 0-vol_home-marker: parent is NULL for <gfid:621f5366-18fa-4d46-8796-4532643d94cd>, aborting updation txn
[2015-08-06 23:44:22.806081] W [marker-quota.c:3379:_mq_initiate_quota_txn] 0-vol_home-marker: parent is NULL for <gfid:621f5366-18fa-4d46-8796-4532643d94cd>, aborting updation txn
[2015-08-06 23:44:22.806107] W [marker-quota.c:3379:_mq_initiate_quota_txn] 0-vol_home-marker: parent is NULL for <gfid:621f5366-18fa-4d46-8796-4532643d94cd>, aborting updation txn

An idea?

Thanks,
Geoffrey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150807/cb5c3661/attachment.html>