Hi All.
On 6/28/21 4:23 AM, wa7skg wrote:
Thanks, but nope. Still doesn't mount on reboot.
Michael
I would like to just drop some ideas here (hope not creating further
confusion)
- First and foremost, in my (short) experience with Rivendell (using
Debian as base OS), I initially used the traditional approach of fstab
the /var/snd mount for the audio storage on the radio network
mockup/labs .... just to realize that, in reality, when acting as a
client, rivendell manages by itself the mounting of /var/snd (this is
not probably, enough documented or highlighted due to its importance, in
the documentation) by means of AUTOFS (so, in debian, I had to install
the autofs package). The autofs parameters (very very similar to those
on a regular fstab) are provided in /etc/rd.conf ...here's an example:
[AudioStore]
MountSource=192.168.1.254:/var/snd
MountType=nfs
MountOptions=rw,rsize=8192,wsize=8192,timeo=14
CaeHostname=
XportHostname=
It works very well to me and it is the 'native' or 'rivendellish' way to
mount /var/snd on the client terminals... Moreover, I think it is worth
to investigate on the /etc/rivendell.d multi-config, rdselect and
rdmonitor because it all it deals with multiple, remote, storage (and
database) mounting/umounting very very nicely (I have learnt to have, on
every terminal on the radio network, two configurations: a local DB and
/var/snd storage config, so it can go 'standalone' , and the networked
DB / NFS /var/snd config)
- Regarding pure fstab issues (again Debian here) I would like to share
that I have had issues too in the recent past, as the operating system
moved deeper and deeper into the realms of systemd management, and I
discovered that classic _netdev and other tricks didn't work anymore,
and some new fstab options are usually required to make systemd managed
machines to mount shares at boot.
If your system is systemd handled (I guess it is) I would look for and
give a try on some fstab options such as x-systemd.automount ,
x-systemd.device-timeout , etc...
Hope this could help
Best regards.
[email protected] wrote on 6/27/21 5:48 PM:
This works for me:
# Rivendell
{IP address of Rivendell Server}:/var/snd /var/snd nfs
auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0
On Sun, Jun 27, 2021 at 5:09 PM wa7skg <[email protected]
<mailto:[email protected]>> wrote:
Two machines in client/server configuration. CentOS7 and RD 3.5.
Set up export stuff on rd1 and fstab on rd2.
rd1:/var/snd /var/snd nfs _netdev,defaults,auto 0 0
However, if I reboot rd2, it does not mount /var/snd from rd1. If I
'sudo mount -a' it mounts fine.
I have inquired about this on other forums with various results
including:
"Your mount does not work because your network/nfs is not up at
the time
/etc/fstab is evaluated."
"NOTE: you mount external /var/snd to local /var/snd which is
definitely bad idea."
"Use autofs"
"Use systemd"
"In your fstab replace “auto” with “noauto,x-systemd.automount”"
Perhaps some of these comments may be useful, but I don't know
how to
implement any of them.
I've been out of this for a few years, and the whole systemd
thing is
still confusing to me.
I've been given a number of setup guides which all have fstab
configurations, but they may be for older versions of stuff.
Is anybody up to date with modern equipment on this?
Thanks for any ideas.
-- 73,
Michael WA7SKG
"Any day you do not learn one new thing is a wasted day."
_______________________________________________
Rivendell-dev mailing list
[email protected]
<mailto:[email protected]>
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
