On Mon, Jun 3, 2019 at 11:57 AM Xie Changlong <zgrep@xxxxxxx> wrote:
Hi allTest gluster 3.8.4-54.15 gnfs, i saw a write request hung in write-behind followed by 1545 FLUSH requests. I found a similar[xlator.performance.write-behind.wb_inode]path=/575/1e/5751e318f21f605f2aac241bf042e7a8.jpginode=0x7f51775b71a0window_conf=1073741824window_current=293822transit-size=293822dontsync=0[.WRITE]request-ptr=0x7f516eec2060refcount=1wound=yesgeneration-number=1req->op_ret=293822req->op_errno=0sync-attempts=1sync-in-progress=yes
Note that the sync is still in progress. This means, write-behind has wound the write-request to its children and yet to receive the response (unless there is a bug in accounting of sync-in-progress). So, its likely that there are callstacks into children of write-behind, which are not complete yet. Are you sure the deepest hung call-stack is in write-behind? Can you check for frames with "complete=0"?
size=293822offset=1048576lied=-1append=0fulfilled=0go=-1[.FLUSH]request-ptr=0x7f517c2badf0refcount=1wound=nogeneration-number=2req->op_ret=-1req->op_errno=116sync-attempts=0[.FLUSH]request-ptr=0x7f5173e9f7b0refcount=1wound=nogeneration-number=2req->op_ret=0req->op_errno=0sync-attempts=0[.FLUSH]request-ptr=0x7f51640b8ca0refcount=1wound=nogeneration-number=2req->op_ret=0req->op_errno=0sync-attempts=0[.FLUSH]request-ptr=0x7f516f3979d0refcount=1wound=nogeneration-number=2req->op_ret=0req->op_errno=0sync-attempts=0[.FLUSH]request-ptr=0x7f516f6ac8d0refcount=1wound=nogeneration-number=2req->op_ret=0req->op_errno=0sync-attempts=0Any comments would be appreciated!Thanks-Xie
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
