From: Scott Mayhew <smayhew@redhat.com>
To: John <therealgraysky@proton.me>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Missing pipe /var/lib/nfs/rpc_pipefs/nfsd/cld on OpenWrt
Date: Thu, 7 Aug 2025 10:25:19 -0400 [thread overview]
Message-ID: <aJS3TwTldSYi8y9g@aion> (raw)
In-Reply-To: <Pm2hmCTqzxzgnGtJpzqYHI5uV7Z7oQjykswavqCewEF_9wqXOJo3_EXS76gIzkpfu9eJLSDlKgNwJrNmTWgD2vKSEr3kLyDsr_Fzzj6jRYs=@proton.me>
On Sat, 02 Aug 2025, John wrote:
> I want to modify the nfs-kernel-server package to use nfsdcld for client tracking, but am hitting a snag: I can't figure out why the pipe /var/lib/nfs/rpc_pipefs/nfsd/cld is missing or what creates it.
>
> Here is my current version: https://github.com/graysky2/packages/commit/c68d0ca16b3b69a0ffcad3dbb20bad58ee49a638
>
> I have the lines in the init script to start /usr/sbin/nfsdcld commented out so it can be run manually with the debug option on the shell to see why it fails. What creates the pipe /var/lib/nfs/rpc_pipefs/nfsd/cld and why is it not doing so is the questions I cannot answer. Any insights are appreciated.
>
> # nfsdcld -F -d
> nfsdcld: sqlite_startup_query_grace: current_epoch=1 recovery_epoch=0
> nfsdcld: sqlite_check_db_health: returning 0
> nfsdcld: sqlite_copy_cltrack_records: returning -1
> nfsdcld: sqlite_prepare_dbh: num_cltrack_records = 0
>
> nfsdcld: sqlite_prepare_dbh: num_legacy_records = 0
>
> nfsdcld: cld_pipe_init: init pipe handlers
> nfsdcld: cld_pipe_open: opening upcall pipe /var/lib/nfs/rpc_pipefs/nfsd/cld
> nfsdcld: cld_pipe_open: open of /var/lib/nfs/rpc_pipefs/nfsd/cld failed: No such file or directory
> nfsdcld: main: Starting event dispatch handler.
>
It gets created when nfsd starts up (see nfsd4_cld_register_sb() in
fs/nfsd/nfs4recover.c). At that point you should see nfsdcld get an
inotify event, open the cld file, and continue doing its thing.
-Scott
prev parent reply other threads:[~2025-08-07 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-02 20:06 Missing pipe /var/lib/nfs/rpc_pipefs/nfsd/cld on OpenWrt John
2025-08-07 14:25 ` Scott Mayhew [this message]
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=aJS3TwTldSYi8y9g@aion \
--to=smayhew@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=therealgraysky@proton.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.