From: Chuck Lever <chuck.lever@oracle.com>
To: Rik Theys <rik.theys@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsd4 laundromat_main hung tasks
Date: Mon, 13 Jan 2025 08:39:18 -0500 [thread overview]
Message-ID: <adef5bc9-254c-412e-8fa8-6f5accedf7f7@oracle.com> (raw)
In-Reply-To: <CAPwv0JmJErKaquZMApyUkpkFn9_x6C+32Dcfxeg0a4-=iR9wEQ@mail.gmail.com>
On 1/13/25 7:30 AM, Rik Theys wrote:
> I've created a systemd unit to run trace-cmd on boot. I've started it
> (before rebooting the system) to see how much disk space would be in
> use by having it running.
> When I stopped it and ran "trace-cmd report", it showed a lot of
> [FAILED TO PARSE] lines, such as:
>
> nfsd-6279 [035] 2560643.942059: nfsd_cb_queue:
> [FAILED TO PARSE] cl_boot=1734210227 cl_id=1829245597
> cb=0xffff94488e9c8d90 need_restart=0 addr=ARRAY[]
> kworker/u192:4-4169949 [032] 2560643.942079: nfsd_cb_start:
> [FAILED TO PARSE] state=0x1 cl_boot=1734210227 cl_id=1829245597
> addr=ARRAY[]
> kworker/u192:4-4169949 [032] 2560643.942081: nfsd_cb_bc_update:
> [FAILED TO PARSE] cl_boot=1734210227 cl_id=1829245597
> cb=0xffff94488e9c8d90 need_restart=0 addr=ARRAY[]
> kworker/u192:4-4169949 [032] 2560643.942082: nfsd_cb_destroy:
> [FAILED TO PARSE] cl_boot=1734210227 cl_id=1829245597
> cb=0xffff94488e9c8d90 need_restart=0 addr=ARRAY[]
> nfsd-6328 [028] 2560643.942503: nfsd_cb_probe:
> [FAILED TO PARSE] state=0x1 cl_boot=1734210227 cl_id=1829245598
> addr=ARRAY[02, 00, 00, 00, 0a, 57, 18, a4, 00, 00, 00, 00, 00, 00, 00,
> 00]
> nfsd-6328 [028] 2560643.942504: nfsd_cb_queue:
> [FAILED TO PARSE] cl_boot=1734210227 cl_id=1829245598
> cb=0xffff94488e9c8300 need_restart=0 addr=ARRAY[02, 00, 00, 00, 0a,
> 57, 18, a4, 00, 00, 00, 00, 00, 00, 00, 00]
> kworker/u192:4-4169949 [032] 2560643.942515: nfsd_cb_start:
> [FAILED TO PARSE] state=0x1 cl_boot=1734210227 cl_id=1829245598
> addr=ARRAY[02, 00, 00, 00, 0a, 57, 18, a4, 00, 00, 00, 00, 00, 00, 00,
> 00]
> kworker/u192:4-4169949 [032] 2560643.942515: nfsd_cb_bc_update:
> [FAILED TO PARSE] cl_boot=1734210227 cl_id=1829245598
> cb=0xffff94488e9c8300 need_restart=0 addr=ARRAY[02, 00, 00, 00, 0a,
> 57, 18, a4, 00, 00, 00, 00, 00, 00, 00, 00]
> kworker/u192:4-4169949 [032] 2560643.942769: nfsd_cb_setup:
> [FAILED TO PARSE] cl_boot=1734210227 cl_id=1829245598 authflavor=0x1
> addr=ARRAY[02, 00, 00, 00, 0a, 57, 18, a4, 00, 00, 00, 00, 00, 00, 00,
> 00] netid=tcp
> kworker/u192:4-4169949 [032] 2560643.942770: nfsd_cb_new_state:
> [FAILED TO PARSE] state=0x0 cl_boot=1734210227 cl_id=1829245598
> addr=ARRAY[02, 00, 00, 00, 0a, 57, 18, a4, 00, 00, 00, 00, 00, 00, 00,
> 00]
> kworker/u192:4-4169949 [032] 2560643.942770: nfsd_cb_destroy:
> [FAILED TO PARSE] cl_boot=1734210227 cl_id=1829245598
> cb=0xffff94488e9c8300 need_restart=0 addr=ARRAY[02, 00, 00, 00, 0a,
> 57, 18, a4, 00, 00, 00, 00, 00, 00, 00, 00]
>
> Is there any additional option I need to specify, or can these items be ignored?
Nope. This means your distribution's user space tracing libraries
are old. The part of these records that failed to parse are the IP
addresses which aren't important for the current exercise.
--
Chuck Lever
next prev parent reply other threads:[~2025-01-13 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 19:49 nfsd4 laundromat_main hung tasks Rik Theys
2025-01-10 20:30 ` Chuck Lever
[not found] ` <CAPwv0J=oKBnCia_mmhm-tYLPqw03jO=LxfUbShSyXFp-mKET5A@mail.gmail.com>
[not found] ` <49654519-9166-4593-ac62-77400cebebb4@oracle.com>
2025-01-12 12:42 ` Rik Theys
2025-01-12 18:57 ` Chuck Lever
2025-01-13 12:30 ` Rik Theys
2025-01-13 13:39 ` Chuck Lever [this message]
2025-01-13 22:12 ` Chuck Lever
2025-01-14 8:23 ` Rik Theys
2025-01-14 14:51 ` Chuck Lever
2025-01-14 15:30 ` Rik Theys
2025-01-14 16:10 ` Chuck Lever
2025-01-14 19:02 ` Chuck Lever
2025-01-16 9:03 ` Rik Theys
2025-01-16 14:12 ` Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adef5bc9-254c-412e-8fa8-6f5accedf7f7@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rik.theys@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox