Ubuntu 18.04 - Mount NFS with FQDN not resolving address
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
Trying to mount /home directories to a NFS share.
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus 0 0
However, in syslog it says that it cannot resolve the address. I'm guessing it'll be OK if I used an IP Address, however this is not feasible due to our storage solution (IP addresses could change at a given moment).
If I mount manually with above in my fstab with the command:
mount -a
It manages to mount fine.
I've also tried creating a systemd service that will do the mount -a command after network is up, but i still get the same problem.
Tried numerous different mounting options, including _netdev.
All help would be greatly appreciated.
18.04 fstab nfs
asked Jun 11 at 8:14
Swinkid
12
add a comment |Â
up vote
0
down vote
favorite
Trying to mount /home directories to a NFS share.
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus 0 0
However, in syslog it says that it cannot resolve the address. I'm guessing it'll be OK if I used an IP Address, however this is not feasible due to our storage solution (IP addresses could change at a given moment).
If I mount manually with above in my fstab with the command:
mount -a
It manages to mount fine.
I've also tried creating a systemd service that will do the mount -a command after network is up, but i still get the same problem.
Tried numerous different mounting options, including _netdev.
All help would be greatly appreciated.
18.04 fstab nfs
asked Jun 11 at 8:14
Swinkid
12
18.04 resolves addresses with systemd-resolved listening on 127.0.0.53:53 (seenetstat -antup. And resolved get his forwarder from the NetworkManager active profile. Seecat /var/run/NetworkManager/resolv.confandcat /var/run/systemd/resolve/resolv.conf... I guess that dns resolution is not ready when the mount command starts.
– cmak.fr
Jun 11 at 8:26
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Trying to mount /home directories to a NFS share.
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus 0 0
However, in syslog it says that it cannot resolve the address. I'm guessing it'll be OK if I used an IP Address, however this is not feasible due to our storage solution (IP addresses could change at a given moment).
If I mount manually with above in my fstab with the command:
mount -a
It manages to mount fine.
I've also tried creating a systemd service that will do the mount -a command after network is up, but i still get the same problem.
Tried numerous different mounting options, including _netdev.
All help would be greatly appreciated.
18.04 fstab nfs
asked Jun 11 at 8:14
Swinkid
12
Trying to mount /home directories to a NFS share.
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus 0 0
However, in syslog it says that it cannot resolve the address. I'm guessing it'll be OK if I used an IP Address, however this is not feasible due to our storage solution (IP addresses could change at a given moment).
If I mount manually with above in my fstab with the command:
mount -a
It manages to mount fine.
I've also tried creating a systemd service that will do the mount -a command after network is up, but i still get the same problem.
Tried numerous different mounting options, including _netdev.
All help would be greatly appreciated.
18.04 fstab nfs
asked Jun 11 at 8:14
Swinkid
12
asked Jun 11 at 8:14
Swinkid
12
asked Jun 11 at 8:14
Swinkid
12
asked Jun 11 at 8:14
Swinkid
12
12
18.04 resolves addresses with systemd-resolved listening on 127.0.0.53:53 (seenetstat -antup. And resolved get his forwarder from the NetworkManager active profile. Seecat /var/run/NetworkManager/resolv.confandcat /var/run/systemd/resolve/resolv.conf... I guess that dns resolution is not ready when the mount command starts.
– cmak.fr
Jun 11 at 8:26
add a comment |Â
18.04 resolves addresses with systemd-resolved listening on 127.0.0.53:53 (seenetstat -antup. And resolved get his forwarder from the NetworkManager active profile. Seecat /var/run/NetworkManager/resolv.confandcat /var/run/systemd/resolve/resolv.conf... I guess that dns resolution is not ready when the mount command starts.
– cmak.fr
Jun 11 at 8:26
18.04 resolves addresses with systemd-resolved listening on 127.0.0.53:53 (see
netstat -antup. And resolved get his forwarder from the NetworkManager active profile. See cat /var/run/NetworkManager/resolv.conf and cat /var/run/systemd/resolve/resolv.conf... I guess that dns resolution is not ready when the mount command starts.– cmak.fr
Jun 11 at 8:26
18.04 resolves addresses with systemd-resolved listening on 127.0.0.53:53 (see
netstat -antup. And resolved get his forwarder from the NetworkManager active profile. See cat /var/run/NetworkManager/resolv.conf and cat /var/run/systemd/resolve/resolv.conf... I guess that dns resolution is not ready when the mount command starts.– cmak.fr
Jun 11 at 8:26
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
To delay nfs mount until newtork is ready, add _netdev to option in the relevant entry in /etc/fstab. Like:
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus,_netdev 0 0
From mount(8) manpage:
_netdev The filesystem resides on a device that requires network access
(used to prevent the system from attempting to mount these filesystems
until the network has been enabled on the system).
answered Jun 11 at 8:52
Soren A
2,8821620
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
To delay nfs mount until newtork is ready, add _netdev to option in the relevant entry in /etc/fstab. Like:
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus,_netdev 0 0
From mount(8) manpage:
_netdev The filesystem resides on a device that requires network access
(used to prevent the system from attempting to mount these filesystems
until the network has been enabled on the system).
answered Jun 11 at 8:52
Soren A
2,8821620
add a comment |Â
up vote
0
down vote
To delay nfs mount until newtork is ready, add _netdev to option in the relevant entry in /etc/fstab. Like:
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus,_netdev 0 0
From mount(8) manpage:
_netdev The filesystem resides on a device that requires network access
(used to prevent the system from attempting to mount these filesystems
until the network has been enabled on the system).
answered Jun 11 at 8:52
Soren A
2,8821620
add a comment |Â
up vote
0
down vote
up vote
0
down vote
To delay nfs mount until newtork is ready, add _netdev to option in the relevant entry in /etc/fstab. Like:
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus,_netdev 0 0
From mount(8) manpage:
_netdev The filesystem resides on a device that requires network access
(used to prevent the system from attempting to mount these filesystems
until the network has been enabled on the system).
answered Jun 11 at 8:52
Soren A
2,8821620
To delay nfs mount until newtork is ready, add _netdev to option in the relevant entry in /etc/fstab. Like:
SERVERURL:/nfstest /home nfs vers=4,proto=tcp,intr,bg,rdirplus,_netdev 0 0
From mount(8) manpage:
_netdev The filesystem resides on a device that requires network access
(used to prevent the system from attempting to mount these filesystems
until the network has been enabled on the system).
answered Jun 11 at 8:52
Soren A
2,8821620
answered Jun 11 at 8:52
Soren A
2,8821620
answered Jun 11 at 8:52
Soren A
2,8821620
answered Jun 11 at 8:52
Soren A
2,8821620
2,8821620
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045532%2fubuntu-18-04-mount-nfs-with-fqdn-not-resolving-address%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
18.04 resolves addresses with systemd-resolved listening on 127.0.0.53:53 (see
netstat -antup. And resolved get his forwarder from the NetworkManager active profile. Seecat /var/run/NetworkManager/resolv.confandcat /var/run/systemd/resolve/resolv.conf... I guess that dns resolution is not ready when the mount command starts.– cmak.fr
Jun 11 at 8:26