Hi Mitchell,

i installed the package and tried to shutdowwn the resource-group.
Still got the error however:

May 23 06:32:53 blofecn2 nfsserver(nfs_daemon)[1282251]: INFO: Stopping 
rpc.statd
May 23 06:32:54 blofecn2 nfsserver(nfs_daemon)[1282251]: INFO: Stop: umount 
(1/10 attempts)
May 23 06:32:54 blofecn2 systemd[1]: export_root-nfs_infodir-rpc_pipefs.mount: 
Deactivated successfully.
May 23 06:32:54 blofecn2 systemd[1]: var-lib-nfs-rpc_pipefs.mount: Deactivated 
successfully.
May 23 06:32:55 blofecn2 nfsserver(nfs_daemon)[1282251]: ERROR: Failed to 
unmount /var/lib/nfs
May 23 06:32:55 blofecn2 nfsserver(nfs_daemon)[1282251]: ERROR: Failed to 
unmount a bind mount
May 23 06:32:55 blofecn2 pacemaker-execd[7826]:  notice: 
nfs_daemon_stop_0[1282251] error output [ umount: /var/lib/nfs: target is busy. 
]
May 23 06:32:55 blofecn2 pacemaker-execd[7826]:  notice: 
nfs_daemon_stop_0[1282251] error output [ ocf-exit-reason:Failed to unmount a 
bind mount ]
May 23 06:32:55 blofecn2 pacemaker-controld[7829]:  notice: Result of stop 
operation for nfs_daemon on blofecn-node2: error (Failed to unmount a bind 
mount) 
May 23 06:32:55 blofecn2 pacemaker-controld[7829]:  notice: 
blofecn-node2-nfs_daemon_stop_0:491 [ umount: /var/lib/nfs: target is 
busy.\nocf-exit-reason:Failed to unmount a bind mount\n ]
May 23 06:32:55 blofecn2 pacemaker-controld[7829]:  notice: Transition 675 
aborted by operation nfs_daemon_stop_0 'modify' on blofecn-node2: Event failed 
May 23 06:32:55 blofecn2 pacemaker-controld[7829]:  notice: Transition 675 
action 133 (nfs_daemon_stop_0 on blofecn-node2): expected 'ok' but got 'error' 
May 23 06:32:55 blofecn2 pacemaker-controld[7829]:  notice: Transition 675 
(Complete=22, Pending=0, Fired=0, Skipped=0, Incomplete=35, 
Source=/var/lib/pacemaker/pengine/pe-input-1098.bz2): Compl
ete
May 23 06:32:55 blofecn2 pacemaker-attrd[7827]:  notice: Setting 
fail-count-nfs_daemon#stop_0[blofecn-node2]: (unset) -> INFINITY 
May 23 06:32:55 blofecn2 pacemaker-attrd[7827]:  notice: Setting 
last-failure-nfs_daemon#stop_0[blofecn-node2]: (unset) -> 1716438775 
May 23 06:32:55 blofecn2 sbd[7086]:  warning: inquisitor_child: pcmk health 
check: UNHEALTHY
May 23 06:32:55 blofecn2 sbd[7086]:  warning: inquisitor_child: Servant pcmk is 
outdated (age: 602589)
May 23 06:32:55 blofecn2 pacemaker-schedulerd[7828]:  warning: Unexpected 
result (error: Failed to unmount a bind mount) was recorded for stop of 
nfs_daemon on blofecn-node2 at May 23 06:32:53 2
024 
May 23 06:32:55 blofecn2 pacemaker-schedulerd[7828]:  warning: Unexpected 
result (error: Failed to unmount a bind mount) was recorded for stop of 
nfs_daemon on blofecn-node2 at May 23 06:32:53 2
024 
May 23 06:32:55 blofecn2 pacemaker-schedulerd[7828]:  warning: Cluster node 
blofecn-node2 will be fenced: nfs_daemon failed there

After that i looked at the mounts a little closer.
My issue seems to be the following:
/dev/mapper/DCSS_VG-nfs_infodir on /export_root/nfs_infodir type ext4 
(rw,relatime)
/dev/mapper/DCSS_VG-nfs_infodir on /var/lib/nfs type ext4 (rw,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
sunrpc on /export_root/nfs_infodir/rpc_pipefs type rpc_pipefs (rw,relatime)

rpc_pipefs is mounted twice, becaufe i originally set the
nfs_shared_infodir to /export_root/nfs_infodir an mounted the Filesystem
there, a bind mount to /var/lib/nfs also creates a second  pipefs mount.

I now switched my nfs_shared_infodir directly to /var/lib/nfs by updating the 
resources.
Now i have only one pipefs mount:

/dev/mapper/DCSS_VG-nfs_infodir on /var/lib/nfs type ext4 (rw,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)

Since i can only test on Thursday i'll report back after 6th of june if
this is working

Best wishes 
Jacob

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065848

Title:
  An ocf:heartbeat:nfsserver resource's stop operation succeeded despite
  the /var/lib/nfs filesystem failing to unmount.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to