From: Scott Mayhew <smayhew@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
linux-nfs@vger.kernel.org, Steve Dickson <steved@redhat.com>
Subject: Re: [nfs-utils] "blkmapd open pipe file /run/rpc_pipefs/nfs/blocklayout failed" and handling of nfs-blkmap.service service
Date: Wed, 14 Jan 2026 07:21:14 -0500 [thread overview]
Message-ID: <aWeKOn18EZYOyLxj@aion> (raw)
In-Reply-To: <aWc5dO3fP4J67x0H@infradead.org>
On Tue, 13 Jan 2026, Christoph Hellwig wrote:
> On Sun, Jan 11, 2026 at 03:17:24PM +0100, Salvatore Bonaccorso wrote:
> > For Debian purposes at least I would like to make things bit less
> > irritating for users, keep ideally the service enabled by default, so
> > that administraors whant to make use of pNFS setup with the
> > blocklayout layout protocol, they just need to make the module load.
>
> The original blocklayout is deprecated because there is almost no
> way to use it safely. So I'd argue for not enabling blkmapd by
> default, and maybe even splitting it into a separate binary package.
>
> Note that none of this affects the revised scsi/nvme layouts that are
> safe to use, and don't require blkmapd.
>
Right, on both Fedora and RHEL nfs-blkmap.service is disabled by default
(via /usr/lib/systemd/system-preset/99-default-disable.preset) because
we support SCSI layout but not block layout. I could have sworn I've
floated the idea of dropping blkmapd from the Red Hat packages
altogether, but I can't find anything in Bugzilla or Jira.
next prev parent reply other threads:[~2026-01-14 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 14:17 [nfs-utils] "blkmapd open pipe file /run/rpc_pipefs/nfs/blocklayout failed" and handling of nfs-blkmap.service service Salvatore Bonaccorso
2026-01-14 6:36 ` Christoph Hellwig
2026-01-14 12:21 ` Scott Mayhew [this message]
2026-01-14 14:54 ` [nfs-utils PATCH] Rename CONFIG_NFSV41 to CONFIG_BLKMAPD and disable by default Scott Mayhew
2026-01-15 16:09 ` Christoph Hellwig
2026-01-15 16:16 ` Salvatore Bonaccorso
2026-01-26 13:37 ` Steve Dickson
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=aWeKOn18EZYOyLxj@aion \
--to=smayhew@redhat.com \
--cc=carnil@debian.org \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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