Hello Ryan,
Aha! Thank you for your good suggestion and confirmation on your setup.
# mount | grep sunrpc
sunrpc on /var/lib/rpc_pipefs type rpc_pipefs (rw)
Given its content, this directory seems to hold client-side info
(only?), which would be perfect to shield from HA handling.
As an aside: I'm mildly confused on the distinction between /etc/
modprobe.conf and /etc/modprobe.d/modprobe.conf.dist , and what, if
any precedence applies for keys in both files - the modprobe.conf(5)
is mum about it. The ".dist" in the file name spells "stay away" to
me. I was googling for an explanation, but the closest I got was from
a discussion in 2004, http://fedoraforum.org/forum/archive/index.php/t-18911.html
, which says "You edit /etc/modprobe.conf if you have to edit
anything" -- alas, there's no context to evaluate whether that's
actually the case.
Regards, Michael
On Sep 13, 2008, at 18:02 , [EMAIL PROTECTED] wrote:
Hi,
I'm running pretty much the same setup. What you're looking for is
located
in /etc/modprobe.d/modprobe.conf and /etc/modprobe.d/dist
Do a search for /var/lib/nfs/rpc_pipefs in those files and replace
it with
/var/lib/rpc_pipefs.
Also, I noticed that the RHEL init scripts for nfs and nfslock were
somewhat broken in my installed (but it was 5.1 at the time of
install so
they may have fixed them with 5.2). The nfs init script wouldn't
kill nfsd
properly and the nfslock init script returned non-LSB compliant
values for
one or more operations (start, stop, status).
--Ryan
Hi,
I am trying to set up HA-NFS on RHEL5.2. I dutifully follow
http://linux-ha.org/HaNFS
, which involves symlinking /var/lib/nfs to shared storage (DRBD-8.x
in my case)
However, like a previous poster, I ran into trouble at /var/lib/nfs/
rpc_pipefs:
rm: cannot remove directory `/var/lib/nfs/rpc_pipefs/statd':
Operation not permitted
see also
http://lists.community.tummy.com/pipermail/linux-ha/2007-January/022977.html
This is because there's a kernel mount active for rpc_pipefs:
# mount | grep sunrpc
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
I think that if I symlink /var/lib/nfs to DRBD, two bad things
happen:
(1) at boot, the DRBD volume is not available, so sunrpc fails to
start. This will definitely happen on the passive node.
(2) if I somehow start sunrpc later, wouldn't that block the umount
of DRBD for failover? (That's moot when all is dead, but it would
block testing or perhaps ordered shutdown.)
Greg Dickie (referenced at the link above) suggested relocating
rpc_pipefs to /var/lib directly, which looks like a good thing to do.
Modifying /etc/idmapd.conf is easy, but the flip side is unclear --
where do I tell *the kernel* (i.e., the sunrpc module) to mount
sunrpc?
Note: The RHEL kernel has the sunrpc module linked in:
# grep sunrpc /var/log/messages | tail -1
Sep 8 00:43:25 mgmt01 kernel: Modules linked in: nfsd exportfs
lockd nfs_acl auth_rpcgss drbd(U) autofs4 ipmi_devintf ipmi_si
ipmi_msghandler hidp rfcomm l2cap bluetooth sunrpc ... <<<
Regards, Michael
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
