On Thu, Feb 18, 2021 at 10:55 AM Timo Rothenpieler <timo@xxxxxxxxxxxxxxxx> wrote: > > On 18.02.2021 14:28, Timo Rothenpieler wrote: > > I'll report back once I got a trace log. > > Find the trace log attached. > It also grabbed quite a bit of unrelated noise, but I think it's still > helpful: > > > nfsd-7226 [025] 2228027.306471: nfsd_compound: xid=0xbca1d6e9 opcnt=5 > > nfsd-7226 [025] 2228027.306472: nfsd_compound_status: op=1/5 OP_SEQUENCE status=0 > > nfsd-7226 [025] 2228027.306479: nfsd_compound_status: op=2/5 OP_PUTFH status=0 > > nfsd-7226 [025] 2228027.306480: nfsd_compound_status: op=3/5 OP_SAVEFH status=0 > > nfsd-7226 [025] 2228027.306483: nfsd_compound_status: op=4/5 OP_PUTFH status=0 > > nfsd-7226 [025] 2228027.306590: nfsd_compound_status: op=5/5 OP_COPY status=0 > > nfsd-7226 [025] 2228027.306702: nfsd_compound: xid=0xbda1d6e9 opcnt=2 > > nfsd-7226 [025] 2228027.306703: nfsd_compound_status: op=1/2 OP_SEQUENCE status=0 > > nfsd-7226 [025] 2228027.306703: nfsd_compound_status: op=2/2 OP_TEST_STATEID status=0 > > nfsd-7226 [025] 2228027.306741: nfsd_compound: xid=0xbea1d6e9 opcnt=2 > > nfsd-7226 [025] 2228027.306742: nfsd_compound_status: op=1/2 OP_SEQUENCE status=0 > > nfsd-7226 [025] 2228027.306747: nfsd_compound_status: op=2/2 OP_TEST_STATEID status=0 > > nfsd-7226 [025] 2228027.306791: nfsd_compound: xid=0xbfa1d6e9 opcnt=2 > > nfsd-7226 [025] 2228027.306792: nfsd_compound_status: op=1/2 OP_SEQUENCE status=0 > > nfsd-7226 [025] 2228027.306793: nfsd_compound_status: op=2/2 OP_TEST_STATEID status=0 > > nfsd-7226 [025] 2228027.306829: nfsd_compound: xid=0xc0a1d6e9 opcnt=2 > > nfsd-7226 [025] 2228027.306830: nfsd_compound_status: op=1/2 OP_SEQUENCE status=0 > > nfsd-7226 [025] 2228027.306831: nfsd_compound_status: op=2/2 OP_TEST_STATEID status=0 > > nfsd-7226 [025] 2228027.306865: nfsd_compound: xid=0xc1a1d6e9 opcnt=2 > > nfsd-7226 [025] 2228027.306866: nfsd_compound_status: op=1/2 OP_SEQUENCE status=0 > > nfsd-7226 [025] 2228027.306866: nfsd_compound_status: op=2/2 OP_TEST_STATEID status=0 > > <...>-2019374 [012] 2228027.307694: nfsd_file_put: hash=0x275 inode=0x0xffffa0c8c35ab490 ref=4 flags=HASHED|REFERENCED may=READ file=0xffffa0e819758800 > > <...>-2019374 [012] 2228027.307694: nfsd_file_put: hash=0x365 inode=0x0xffffa0d70dd5dec0 ref=5 flags=HASHED|REFERENCED may=READ|WRITE file=0xffffa0e819759000 > > <...>-2019374 [012] 2228027.307701: nfsd_file_put: hash=0x365 inode=0x0xffffa0d70dd5dec0 ref=4 flags=HASHED|REFERENCED may=READ|WRITE file=0xffffa0e819759000 > > <...>-2019374 [012] 2228027.307701: nfsd_file_put: hash=0x275 inode=0x0xffffa0c8c35ab490 ref=3 flags=HASHED|REFERENCED may=READ file=0xffffa0e819758800 > > <...>-1885588 [029] 2228027.307725: nfsd_cb_work: addr=10.110.10.252:0 client 600c8efc:868a6681 procedure=CB_OFFLOAD > > <...>-1885588 [029] 2228027.307746: nfsd_cb_done: addr=10.110.10.252:0 client 600c8efc:868a6681 status=-107 > > <...>-1885588 [029] 2228027.307747: nfsd_cb_state: addr=10.110.10.252:0 client 600c8efc:868a6681 state=FAULT Thank you for getting tracepoints from a busy server but can you get more? As suspected, the server is having issues sending the callback. I'm not sure why. Any chance to turn on the server's sunrpc tracespoints, probably both sunrpc and rdmas tracepoints, I wonder if we can any more info about why it's failing?
