systemd seems to ignore _netdev option for NFS in Ubuntu 16.04 Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)NAS won't mount at boot but will mount with mount command after bootUbuntu 12.04 NFS v4 mount error incorrect mount option was specifiedUbuntu NFS ServerHow to mount a NFS share in Ubuntu 16.04?NFS mounts not working in ubuntu 16.04?nfs mount connection time out ubuntu 16.04Ubuntu NFS Client mounts but doesn't see files on Win 2008 Server16.04 nfs mount problems at boot timeUbuntu 18.04 - Mount NFS with FQDN not resolving addressNFS Share Permissions -Ubuntu 16.04Systemd mount.nfs fails: Network is unreachable on Ubuntu 16.04
When the Haste spell ends on a creature, do attackers have advantage against that creature?
Can you use the Shield Master feat to shove someone before you make an attack by using a Readied action?
Generate an RGB colour grid
Wu formula for manifolds with boundary
How to answer "Have you ever been terminated?"
When a candle burns, why does the top of wick glow if bottom of flame is hottest?
Using audio cues to encourage good posture
Denied boarding although I have proper visa and documentation. To whom should I make a complaint?
What would be the ideal power source for a cybernetic eye?
What is the longest distance a player character can jump in one leap?
For a new assistant professor in CS, how to build/manage a publication pipeline
Trademark violation for app?
Do square wave exist?
Is this homebrew Lady of Pain warlock patron balanced?
What is homebrew?
Why didn't Eitri join the fight?
Did MS DOS itself ever use blinking text?
Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?
Does classifying an integer as a discrete log require it be part of a multiplicative group?
Significance of Cersei's obsession with elephants?
What is the meaning of the simile “quick as silk”?
Is safe to use va_start macro with this as parameter?
What do you call the main part of a joke?
What are the out-of-universe reasons for the references to Toby Maguire-era Spider-Man in ITSV
systemd seems to ignore _netdev option for NFS in Ubuntu 16.04
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)NAS won't mount at boot but will mount with mount command after bootUbuntu 12.04 NFS v4 mount error incorrect mount option was specifiedUbuntu NFS ServerHow to mount a NFS share in Ubuntu 16.04?NFS mounts not working in ubuntu 16.04?nfs mount connection time out ubuntu 16.04Ubuntu NFS Client mounts but doesn't see files on Win 2008 Server16.04 nfs mount problems at boot timeUbuntu 18.04 - Mount NFS with FQDN not resolving addressNFS Share Permissions -Ubuntu 16.04Systemd mount.nfs fails: Network is unreachable on Ubuntu 16.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have the following mount for NFS in /etc/fstab:
192.168.1.6:/var/share /media/share nfs hard,intr,retrans=10,timeo=10000000,_netdev 0 0
On reboot my system hangs; turns out it's the mount as proved by systemd-analyze blame.
The status:
● media-share.mount - /media/share
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2016-04-26 21:13:43 EDT; 6min ago
Where: /media/share
What: 192.168.1.6:/var/share
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1071 ExecMount=/bin/mount 192.168.1.6:/var/share /media/share -t nfs -o hard,intr,retrans=10,timeo=10000000,_netdev (code=kille
Apr 26 21:12:12 j-Lemur systemd[1]: Mounting /media/share...
Apr 26 21:13:42 j-Lemur systemd[1]: media-share.mount: Mounting timed out. Stopping.
Apr 26 21:13:42 j-Lemur systemd[1]: Mounted /media/share.
Apr 26 21:13:43 j-Lemur systemd[1]: media-share.mount: Unit entered failed state.
This appears to be a bug?
After logging in and running systemctl restart media-share.mount it is fixed (because the network is available now).
mount nfs systemd
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
add a comment |
I have the following mount for NFS in /etc/fstab:
192.168.1.6:/var/share /media/share nfs hard,intr,retrans=10,timeo=10000000,_netdev 0 0
On reboot my system hangs; turns out it's the mount as proved by systemd-analyze blame.
The status:
● media-share.mount - /media/share
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2016-04-26 21:13:43 EDT; 6min ago
Where: /media/share
What: 192.168.1.6:/var/share
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1071 ExecMount=/bin/mount 192.168.1.6:/var/share /media/share -t nfs -o hard,intr,retrans=10,timeo=10000000,_netdev (code=kille
Apr 26 21:12:12 j-Lemur systemd[1]: Mounting /media/share...
Apr 26 21:13:42 j-Lemur systemd[1]: media-share.mount: Mounting timed out. Stopping.
Apr 26 21:13:42 j-Lemur systemd[1]: Mounted /media/share.
Apr 26 21:13:43 j-Lemur systemd[1]: media-share.mount: Unit entered failed state.
This appears to be a bug?
After logging in and running systemctl restart media-share.mount it is fixed (because the network is available now).
mount nfs systemd
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
add a comment |
I have the following mount for NFS in /etc/fstab:
192.168.1.6:/var/share /media/share nfs hard,intr,retrans=10,timeo=10000000,_netdev 0 0
On reboot my system hangs; turns out it's the mount as proved by systemd-analyze blame.
The status:
● media-share.mount - /media/share
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2016-04-26 21:13:43 EDT; 6min ago
Where: /media/share
What: 192.168.1.6:/var/share
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1071 ExecMount=/bin/mount 192.168.1.6:/var/share /media/share -t nfs -o hard,intr,retrans=10,timeo=10000000,_netdev (code=kille
Apr 26 21:12:12 j-Lemur systemd[1]: Mounting /media/share...
Apr 26 21:13:42 j-Lemur systemd[1]: media-share.mount: Mounting timed out. Stopping.
Apr 26 21:13:42 j-Lemur systemd[1]: Mounted /media/share.
Apr 26 21:13:43 j-Lemur systemd[1]: media-share.mount: Unit entered failed state.
This appears to be a bug?
After logging in and running systemctl restart media-share.mount it is fixed (because the network is available now).
mount nfs systemd
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
I have the following mount for NFS in /etc/fstab:
192.168.1.6:/var/share /media/share nfs hard,intr,retrans=10,timeo=10000000,_netdev 0 0
On reboot my system hangs; turns out it's the mount as proved by systemd-analyze blame.
The status:
● media-share.mount - /media/share
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2016-04-26 21:13:43 EDT; 6min ago
Where: /media/share
What: 192.168.1.6:/var/share
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1071 ExecMount=/bin/mount 192.168.1.6:/var/share /media/share -t nfs -o hard,intr,retrans=10,timeo=10000000,_netdev (code=kille
Apr 26 21:12:12 j-Lemur systemd[1]: Mounting /media/share...
Apr 26 21:13:42 j-Lemur systemd[1]: media-share.mount: Mounting timed out. Stopping.
Apr 26 21:13:42 j-Lemur systemd[1]: Mounted /media/share.
Apr 26 21:13:43 j-Lemur systemd[1]: media-share.mount: Unit entered failed state.
This appears to be a bug?
After logging in and running systemctl restart media-share.mount it is fixed (because the network is available now).
mount nfs systemd
mount nfs systemd
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
asked Apr 27 '16 at 1:29
user1529891user1529891
2,36821522
2,36821522
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I had the same problem.
There's some info on the Ubuntu Community Help Wiki here suggesting it is intentional behaviour by Ubuntu 16:
Under NFSv3 (type nfs) the _netdev option will tell the system to wait to mount until the network is available. With a type of nfs4 this option is ignored, but can be used with mount -O _netdev in scripts later. Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up.
My solution was to the add "vers=3" before "_netdev", forcing the connection to use NFS v3. Obviously this might not help in your case, if you are relying on NFS v4.
Other options could include AutoFS or shell scripting.
answered Jun 15 '16 at 14:33
zek19zek19
1011
The "Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up" text has been there since long before systemd integration, which is supposed to take care of this. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=835810 for example. The fact the systemd-fstab-generator produces units that have "Wants=network-online.target" is further evidence that this is intended to work.
– Dominic Scheirlinck
May 10 '17 at 0:18
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f763498%2fsystemd-seems-to-ignore-netdev-option-for-nfs-in-ubuntu-16-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same problem.
There's some info on the Ubuntu Community Help Wiki here suggesting it is intentional behaviour by Ubuntu 16:
Under NFSv3 (type nfs) the _netdev option will tell the system to wait to mount until the network is available. With a type of nfs4 this option is ignored, but can be used with mount -O _netdev in scripts later. Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up.
My solution was to the add "vers=3" before "_netdev", forcing the connection to use NFS v3. Obviously this might not help in your case, if you are relying on NFS v4.
Other options could include AutoFS or shell scripting.
answered Jun 15 '16 at 14:33
zek19zek19
1011
The "Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up" text has been there since long before systemd integration, which is supposed to take care of this. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=835810 for example. The fact the systemd-fstab-generator produces units that have "Wants=network-online.target" is further evidence that this is intended to work.
– Dominic Scheirlinck
May 10 '17 at 0:18
add a comment |
I had the same problem.
There's some info on the Ubuntu Community Help Wiki here suggesting it is intentional behaviour by Ubuntu 16:
Under NFSv3 (type nfs) the _netdev option will tell the system to wait to mount until the network is available. With a type of nfs4 this option is ignored, but can be used with mount -O _netdev in scripts later. Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up.
My solution was to the add "vers=3" before "_netdev", forcing the connection to use NFS v3. Obviously this might not help in your case, if you are relying on NFS v4.
Other options could include AutoFS or shell scripting.
answered Jun 15 '16 at 14:33
zek19zek19
1011
The "Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up" text has been there since long before systemd integration, which is supposed to take care of this. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=835810 for example. The fact the systemd-fstab-generator produces units that have "Wants=network-online.target" is further evidence that this is intended to work.
– Dominic Scheirlinck
May 10 '17 at 0:18
add a comment |
I had the same problem.
There's some info on the Ubuntu Community Help Wiki here suggesting it is intentional behaviour by Ubuntu 16:
Under NFSv3 (type nfs) the _netdev option will tell the system to wait to mount until the network is available. With a type of nfs4 this option is ignored, but can be used with mount -O _netdev in scripts later. Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up.
My solution was to the add "vers=3" before "_netdev", forcing the connection to use NFS v3. Obviously this might not help in your case, if you are relying on NFS v4.
Other options could include AutoFS or shell scripting.
answered Jun 15 '16 at 14:33
zek19zek19
1011
I had the same problem.
There's some info on the Ubuntu Community Help Wiki here suggesting it is intentional behaviour by Ubuntu 16:
Under NFSv3 (type nfs) the _netdev option will tell the system to wait to mount until the network is available. With a type of nfs4 this option is ignored, but can be used with mount -O _netdev in scripts later. Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up.
My solution was to the add "vers=3" before "_netdev", forcing the connection to use NFS v3. Obviously this might not help in your case, if you are relying on NFS v4.
Other options could include AutoFS or shell scripting.
answered Jun 15 '16 at 14:33
zek19zek19
1011
answered Jun 15 '16 at 14:33
zek19zek19
1011
answered Jun 15 '16 at 14:33
zek19zek19
1011
answered Jun 15 '16 at 14:33
zek19zek19
1011
1011
The "Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up" text has been there since long before systemd integration, which is supposed to take care of this. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=835810 for example. The fact the systemd-fstab-generator produces units that have "Wants=network-online.target" is further evidence that this is intended to work.
– Dominic Scheirlinck
May 10 '17 at 0:18
add a comment |
The "Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up" text has been there since long before systemd integration, which is supposed to take care of this. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=835810 for example. The fact the systemd-fstab-generator produces units that have "Wants=network-online.target" is further evidence that this is intended to work.
– Dominic Scheirlinck
May 10 '17 at 0:18
The "Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up" text has been there since long before systemd integration, which is supposed to take care of this. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=835810 for example. The fact the systemd-fstab-generator produces units that have "Wants=network-online.target" is further evidence that this is intended to work.
– Dominic Scheirlinck
May 10 '17 at 0:18
The "Currently Ubuntu Server does not come with the scripts needed to auto-mount nfs4 entries in /etc/fstab after the network is up" text has been there since long before systemd integration, which is supposed to take care of this. See bugs.debian.org/cgi-bin/bugreport.cgi?bug=835810 for example. The fact the systemd-fstab-generator produces units that have "Wants=network-online.target" is further evidence that this is intended to work.
– Dominic Scheirlinck
May 10 '17 at 0:18
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f763498%2fsystemd-seems-to-ignore-netdev-option-for-nfs-in-ubuntu-16-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
