Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Start nfs-blkmap.service without blocklayoutdriver warn as blkmapd: open pipe file /var/lib/nfs/rpc_pipefs/nfs/blocklayout failed: No such file or directory (RHEL8)
This also exists in RHEL8.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[22:36:57 root@ ~~]# lsmod | grep blocklayoutdriver
[22:36:57 root@ ~~]# service nfs-blkmap restart
Redirecting to /bin/systemctl restart nfs-blkmap.service
[22:36:57 root@ ~~]# service nfs-blkmap status
Redirecting to /bin/systemctl status nfs-blkmap.service
* nfs-blkmap.service - pNFS block layout mapping daemon
Loaded: loaded (/usr/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2019-09-04 22:36:57 EDT; 50ms ago
Process: 7461 ExecStart=/usr/sbin/blkmapd (code=exited, status=0/SUCCESS)
Main PID: 7462 (blkmapd)
Tasks: 1 (limit: 26213)
Memory: 1.0M
CGroup: /system.slice/nfs-blkmap.service
`-7462 /usr/sbin/blkmapd
Sep 04 22:36:57 rhel-8.1.0.redhat.com systemd[1]: Starting pNFS block layout mapping daemon...
Sep 04 22:36:57 rhel-8.1.0.redhat.com blkmapd[7462]: open pipe file /var/lib/nfs/rpc_pipefs/nfs/blocklayout failed: No such file or directory <<<<<<<<
Sep 04 22:36:57 rhel-8.1.0.redhat.com systemd[1]: Started pNFS block layout mapping daemon.
P.S.
This warning only occurs when module "blocklayoutdriver" not loaded.
However, even after loading the module, there might be another warning, i.e.
Bug 1753828 - [blkmapd] systemd: Can't open PID file /var/run/blkmapd.pid (yet?) after start: No such file or directory (RHEL8)
+++ This bug was initially created as a clone of Bug #1753865 +++
Description of problem:
As rhel7 Bug 1563319 says, the NFS client should be able to automatically load module "blocklayoutdriver".
But seems there is always a blkmapd warning after starting nfs-blkmap.service:
"""
blkmapd[43744]: open pipe file /var/lib/nfs/rpc_pipefs/nfs/blocklayout failed: No such file or directory
"""
However, it doesn't affect the following function.
I'm not sure whether this is a real bug. But in the future may receive some complain as more customers using this scenario.
Version-Release number of selected component (if applicable):
nfs-utils-1.3.0-0.65.el7
How reproducible:
always
Steps to Reproduce:
1. modprobe -r blocklayoutdriver
2. systemctl restart nfs-blkmap.service
3. systemctl status nfs-blkmap.service
(In reply to Yongcheng Yang from comment #0)
> ...
>
> Steps to Reproduce:
> 1. modprobe -r blocklayoutdriver
> 2. systemctl restart nfs-blkmap.service
> 3. systemctl status nfs-blkmap.service
Looks like the blocklayoutdriver is not loaded automatically even though the nfs-blkmap server has been bring up.
There's some inconsistency between the module and service config IMO.
[root@hp-dl385pg8-09 ~]# rpm -q nfs-utils
nfs-utils-2.3.3-35.el8.x86_64
[root@hp-dl385pg8-09 ~]# lsmod | grep blocklayoutdriver
[root@hp-dl385pg8-09 ~]# systemctl restart nfs-blkmap && systemctl status nfs-blkmap.service
● nfs-blkmap.service - pNFS block layout mapping daemon
Loaded: loaded (/usr/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: disabled)
Active: active (running) (thawing) since Mon 2020-10-26 04:17:05 EDT; 100ms ago
Process: 28742 ExecStart=/usr/sbin/blkmapd (code=exited, status=0/SUCCESS)
Main PID: 28744 (blkmapd)
Tasks: 1 (limit: 204052)
Memory: 1.4M
CGroup: /system.slice/nfs-blkmap.service
└─28744 /usr/sbin/blkmapd
Oct 26 04:17:05 hp-dl385pg8-09.rhts.eng.pek2.redhat.com systemd[1]: Starting pNFS block layout mapping daemon...
Oct 26 04:17:05 hp-dl385pg8-09.rhts.eng.pek2.redhat.com blkmapd[28744]: open pipe file /var/lib/nfs/rpc_pipefs/nfs/blocklayout failed: No su>
Oct 26 04:17:05 hp-dl385pg8-09.rhts.eng.pek2.redhat.com systemd[1]: Started pNFS block layout mapping daemon.
[root@hp-dl385pg8-09 ~]# cat /var/run/blkmapd.pid
28744
[root@hp-dl385pg8-09 ~]# ps 28744
PID TTY STAT TIME COMMAND
28744 ? Ss 0:00 /usr/sbin/blkmapd
[root@hp-dl385pg8-09 ~]# lsmod | grep blocklayoutdriver
[root@hp-dl385pg8-09 ~]# <<<<<<<<<<<<<<<
Comment 7RHEL Program Management
2021-03-20 07:30:45 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
This also exists in RHEL8. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [22:36:57 root@ ~~]# lsmod | grep blocklayoutdriver [22:36:57 root@ ~~]# service nfs-blkmap restart Redirecting to /bin/systemctl restart nfs-blkmap.service [22:36:57 root@ ~~]# service nfs-blkmap status Redirecting to /bin/systemctl status nfs-blkmap.service * nfs-blkmap.service - pNFS block layout mapping daemon Loaded: loaded (/usr/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2019-09-04 22:36:57 EDT; 50ms ago Process: 7461 ExecStart=/usr/sbin/blkmapd (code=exited, status=0/SUCCESS) Main PID: 7462 (blkmapd) Tasks: 1 (limit: 26213) Memory: 1.0M CGroup: /system.slice/nfs-blkmap.service `-7462 /usr/sbin/blkmapd Sep 04 22:36:57 rhel-8.1.0.redhat.com systemd[1]: Starting pNFS block layout mapping daemon... Sep 04 22:36:57 rhel-8.1.0.redhat.com blkmapd[7462]: open pipe file /var/lib/nfs/rpc_pipefs/nfs/blocklayout failed: No such file or directory <<<<<<<< Sep 04 22:36:57 rhel-8.1.0.redhat.com systemd[1]: Started pNFS block layout mapping daemon. P.S. This warning only occurs when module "blocklayoutdriver" not loaded. However, even after loading the module, there might be another warning, i.e. Bug 1753828 - [blkmapd] systemd: Can't open PID file /var/run/blkmapd.pid (yet?) after start: No such file or directory (RHEL8) +++ This bug was initially created as a clone of Bug #1753865 +++ Description of problem: As rhel7 Bug 1563319 says, the NFS client should be able to automatically load module "blocklayoutdriver". But seems there is always a blkmapd warning after starting nfs-blkmap.service: """ blkmapd[43744]: open pipe file /var/lib/nfs/rpc_pipefs/nfs/blocklayout failed: No such file or directory """ However, it doesn't affect the following function. I'm not sure whether this is a real bug. But in the future may receive some complain as more customers using this scenario. Version-Release number of selected component (if applicable): nfs-utils-1.3.0-0.65.el7 How reproducible: always Steps to Reproduce: 1. modprobe -r blocklayoutdriver 2. systemctl restart nfs-blkmap.service 3. systemctl status nfs-blkmap.service