NFS Binding Issue

Latest response

I have a server configured with sftp jailed account(sftpxyz) under /chroots/sftpxyz

Did binding of /usr/sap/bac/LAE to /chroots/sftpxyz/LAE , where /usr/sap/bac/LAE is an NFS share coming from Isilon storage

To keep it persistent across reboot made an entry in /etc/fstab ,
/usr/sap/bac/LAE /chroots/sftpxyz/LAE none defaults,bind 0 0

df -h

kopisiloncl01:/ifs/data/sap/
100G 12G 87G 13% /usr/sap/

Problem:
The mounting of /usr/sap/bac/LAE is FAILING after the reboot.. Reason being, the NFS service starts after the mounting attempt of /chroots

Remounting root filesystem in read-write mode: [ OK ]
Mounting local filesystems: mount: special device /usr/sap/bac/LAE does not exist
mount: special device /usr/sap/bac/LAE does not exist
[FAILED]
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: [ OK ]
Starting automount: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS mountd: [ OK ]
Starting NFS daemon: [ OK ]
Starting RPC idmapd: [ OK ]

Workaround: Currently, after the reboot of the server, i am manually remount /chroot/sftpxyz

Question:
1. How to come over this issue? If i change the boot order of NFS or chroots what will be the impact ?

Responses

You should be able to set dependencies for other mounts https://www.freedesktop.org/software/systemd/man/systemd.mount.html

Sorry forgot to mention this is RHEL 6.7 systems.

Also, wondering adding NETWORKDELAY=60 in /etc/sysconfig/network will solve this problem.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.