I’m using influxdb on my Raspberry Pi in combination with a NFS mount. The NFS mount is on my Synology NAS and should store the database data of influxdb. Reason for this setup is that I fear that the SD card won’t survive the many write/read cycles caused by a database writing to it.
The shared folder on my Synology is configured to be accessible by various IPs in my network:
The problem with Raspbian is that I’ve tried to auto mount the NFS share on startup, so that the influxdb service can directly write to the NFS mount.
I’ve used these settings in my /etc/fstab to mount the volume automatically:
<DS IP>:/volume1/databases /mnt/databases nfs auto,user,rw,nolock,nosuid 0 0
This doesn’t work properly since my influxdb is often dead after a restart, but if I check the mounted volumes I see the NFS volume mounted properly.
However, there’s a tool called autofs which already helped me with a similar problem on my Mac when I moved my iTunes library to the Synology share.
Install autofs using
sudo apt-get install autofs
Open the file /etc/auto.master and add something like this
/mnt /etc/auto.databases -nosuid,noowners
Now create a file called /etc/auto.databases with this content
databases -fstype=nfs,user,nolock,nosuid,rw <DS IP>:/volume1/databases
Unmount the existing NFS share. Remove/comment out the line for the nfs mount in your /etc/fstab so that it doesn’t conflict with autofs. Restart autofs with
sudo service autofs restart
Now check the content of your mount point with e.g.
Autofs should now automatically mount the NFS share. This might take a while, which is a good sign that the mount is loaded. You can also verify with
that your NFS share is mounted to e.g. /mnt/databases. If you’ll restart now, influxdb should be happy on restart. When it tries to start, autofs will see the access to the mounted folder and will mount the NFS share before influxdb can start up properly.