How can I troubleshoot a mount issue when moving to Systemd (14.04 > 16.04)?












1















I have a data server and two VMs. The first VM, clone14, runs Ubuntu 14.04. The second VM, clone16, was cloned from clone14 and then upgraded to Ubuntu 16.04.



Both VMs have the exact same /etc/fstab file that includes a line mounting a directory from the data server, whose IP address is 99.99.99.99 in this example:



99.99.99.99:/data/NFS/primary            /disks          nfs     rw,soft,intr,actimeo=60 0 0


Everything always works as intended on clone14, but clone16 will not consistently mount the remote directory. Sometimes it will partially mount it, with only some of the subdirectories and files available within the clone16:/disks/ mountpoint.



The big change from 14.04 to 16.04 is Systemd instead of Upstart as the init system. Systemd is supposed to accept fstab entries without a problem, but something is clearly messing up here.



I've searched for "update fstab for systemd" and related terms, but I haven't found anything I can interpret as useful. This post contains almost my entire knowledge of fstab and mounting in Linux, so please use small words when responding. As always, context and explanation in your comments and answers are valuable to me and others who find this page in the future.



How do I figure out what's wrong and correct it?










share|improve this question























  • I think that you need to replace nfs with cifs in your mount statement.

    – heynnema
    Feb 21 at 16:29











  • @heynnema What makes you say that? I can't find any indication that nfs won't work with Ubuntu 16.04/Systemd, or that it has been superseded by cifs

    – Borea Deitz
    Feb 21 at 18:25











  • Before asking the question, did you try cifs to see if it works for you?

    – heynnema
    Feb 21 at 18:51











  • @heynnema No, I didn't. Wouldn't the data server need to be configured for cifs? And isn't cifs a Windows thing?

    – Borea Deitz
    Feb 21 at 19:05











  • Network shares is not my area of expertise... I just seem to remember that cifs has been the fix for a few questions that I've seen. Maybe I'm wrong. But... it would take as long to try cifs, as we've been discussing it. If it doesn't work, I can admit to being wrong :-) You may also have to change some of the optional parameters in your statement.

    – heynnema
    Feb 21 at 19:08


















1















I have a data server and two VMs. The first VM, clone14, runs Ubuntu 14.04. The second VM, clone16, was cloned from clone14 and then upgraded to Ubuntu 16.04.



Both VMs have the exact same /etc/fstab file that includes a line mounting a directory from the data server, whose IP address is 99.99.99.99 in this example:



99.99.99.99:/data/NFS/primary            /disks          nfs     rw,soft,intr,actimeo=60 0 0


Everything always works as intended on clone14, but clone16 will not consistently mount the remote directory. Sometimes it will partially mount it, with only some of the subdirectories and files available within the clone16:/disks/ mountpoint.



The big change from 14.04 to 16.04 is Systemd instead of Upstart as the init system. Systemd is supposed to accept fstab entries without a problem, but something is clearly messing up here.



I've searched for "update fstab for systemd" and related terms, but I haven't found anything I can interpret as useful. This post contains almost my entire knowledge of fstab and mounting in Linux, so please use small words when responding. As always, context and explanation in your comments and answers are valuable to me and others who find this page in the future.



How do I figure out what's wrong and correct it?










share|improve this question























  • I think that you need to replace nfs with cifs in your mount statement.

    – heynnema
    Feb 21 at 16:29











  • @heynnema What makes you say that? I can't find any indication that nfs won't work with Ubuntu 16.04/Systemd, or that it has been superseded by cifs

    – Borea Deitz
    Feb 21 at 18:25











  • Before asking the question, did you try cifs to see if it works for you?

    – heynnema
    Feb 21 at 18:51











  • @heynnema No, I didn't. Wouldn't the data server need to be configured for cifs? And isn't cifs a Windows thing?

    – Borea Deitz
    Feb 21 at 19:05











  • Network shares is not my area of expertise... I just seem to remember that cifs has been the fix for a few questions that I've seen. Maybe I'm wrong. But... it would take as long to try cifs, as we've been discussing it. If it doesn't work, I can admit to being wrong :-) You may also have to change some of the optional parameters in your statement.

    – heynnema
    Feb 21 at 19:08
















1












1








1








I have a data server and two VMs. The first VM, clone14, runs Ubuntu 14.04. The second VM, clone16, was cloned from clone14 and then upgraded to Ubuntu 16.04.



Both VMs have the exact same /etc/fstab file that includes a line mounting a directory from the data server, whose IP address is 99.99.99.99 in this example:



99.99.99.99:/data/NFS/primary            /disks          nfs     rw,soft,intr,actimeo=60 0 0


Everything always works as intended on clone14, but clone16 will not consistently mount the remote directory. Sometimes it will partially mount it, with only some of the subdirectories and files available within the clone16:/disks/ mountpoint.



The big change from 14.04 to 16.04 is Systemd instead of Upstart as the init system. Systemd is supposed to accept fstab entries without a problem, but something is clearly messing up here.



I've searched for "update fstab for systemd" and related terms, but I haven't found anything I can interpret as useful. This post contains almost my entire knowledge of fstab and mounting in Linux, so please use small words when responding. As always, context and explanation in your comments and answers are valuable to me and others who find this page in the future.



How do I figure out what's wrong and correct it?










share|improve this question














I have a data server and two VMs. The first VM, clone14, runs Ubuntu 14.04. The second VM, clone16, was cloned from clone14 and then upgraded to Ubuntu 16.04.



Both VMs have the exact same /etc/fstab file that includes a line mounting a directory from the data server, whose IP address is 99.99.99.99 in this example:



99.99.99.99:/data/NFS/primary            /disks          nfs     rw,soft,intr,actimeo=60 0 0


Everything always works as intended on clone14, but clone16 will not consistently mount the remote directory. Sometimes it will partially mount it, with only some of the subdirectories and files available within the clone16:/disks/ mountpoint.



The big change from 14.04 to 16.04 is Systemd instead of Upstart as the init system. Systemd is supposed to accept fstab entries without a problem, but something is clearly messing up here.



I've searched for "update fstab for systemd" and related terms, but I haven't found anything I can interpret as useful. This post contains almost my entire knowledge of fstab and mounting in Linux, so please use small words when responding. As always, context and explanation in your comments and answers are valuable to me and others who find this page in the future.



How do I figure out what's wrong and correct it?







mount fstab systemd






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 21 at 15:34









Borea DeitzBorea Deitz

83




83













  • I think that you need to replace nfs with cifs in your mount statement.

    – heynnema
    Feb 21 at 16:29











  • @heynnema What makes you say that? I can't find any indication that nfs won't work with Ubuntu 16.04/Systemd, or that it has been superseded by cifs

    – Borea Deitz
    Feb 21 at 18:25











  • Before asking the question, did you try cifs to see if it works for you?

    – heynnema
    Feb 21 at 18:51











  • @heynnema No, I didn't. Wouldn't the data server need to be configured for cifs? And isn't cifs a Windows thing?

    – Borea Deitz
    Feb 21 at 19:05











  • Network shares is not my area of expertise... I just seem to remember that cifs has been the fix for a few questions that I've seen. Maybe I'm wrong. But... it would take as long to try cifs, as we've been discussing it. If it doesn't work, I can admit to being wrong :-) You may also have to change some of the optional parameters in your statement.

    – heynnema
    Feb 21 at 19:08





















  • I think that you need to replace nfs with cifs in your mount statement.

    – heynnema
    Feb 21 at 16:29











  • @heynnema What makes you say that? I can't find any indication that nfs won't work with Ubuntu 16.04/Systemd, or that it has been superseded by cifs

    – Borea Deitz
    Feb 21 at 18:25











  • Before asking the question, did you try cifs to see if it works for you?

    – heynnema
    Feb 21 at 18:51











  • @heynnema No, I didn't. Wouldn't the data server need to be configured for cifs? And isn't cifs a Windows thing?

    – Borea Deitz
    Feb 21 at 19:05











  • Network shares is not my area of expertise... I just seem to remember that cifs has been the fix for a few questions that I've seen. Maybe I'm wrong. But... it would take as long to try cifs, as we've been discussing it. If it doesn't work, I can admit to being wrong :-) You may also have to change some of the optional parameters in your statement.

    – heynnema
    Feb 21 at 19:08



















I think that you need to replace nfs with cifs in your mount statement.

– heynnema
Feb 21 at 16:29





I think that you need to replace nfs with cifs in your mount statement.

– heynnema
Feb 21 at 16:29













@heynnema What makes you say that? I can't find any indication that nfs won't work with Ubuntu 16.04/Systemd, or that it has been superseded by cifs

– Borea Deitz
Feb 21 at 18:25





@heynnema What makes you say that? I can't find any indication that nfs won't work with Ubuntu 16.04/Systemd, or that it has been superseded by cifs

– Borea Deitz
Feb 21 at 18:25













Before asking the question, did you try cifs to see if it works for you?

– heynnema
Feb 21 at 18:51





Before asking the question, did you try cifs to see if it works for you?

– heynnema
Feb 21 at 18:51













@heynnema No, I didn't. Wouldn't the data server need to be configured for cifs? And isn't cifs a Windows thing?

– Borea Deitz
Feb 21 at 19:05





@heynnema No, I didn't. Wouldn't the data server need to be configured for cifs? And isn't cifs a Windows thing?

– Borea Deitz
Feb 21 at 19:05













Network shares is not my area of expertise... I just seem to remember that cifs has been the fix for a few questions that I've seen. Maybe I'm wrong. But... it would take as long to try cifs, as we've been discussing it. If it doesn't work, I can admit to being wrong :-) You may also have to change some of the optional parameters in your statement.

– heynnema
Feb 21 at 19:08







Network shares is not my area of expertise... I just seem to remember that cifs has been the fix for a few questions that I've seen. Maybe I'm wrong. But... it would take as long to try cifs, as we've been discussing it. If it doesn't work, I can admit to being wrong :-) You may also have to change some of the optional parameters in your statement.

– heynnema
Feb 21 at 19:08












0






active

oldest

votes












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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120156%2fhow-can-i-troubleshoot-a-mount-issue-when-moving-to-systemd-14-04-16-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120156%2fhow-can-i-troubleshoot-a-mount-issue-when-moving-to-systemd-14-04-16-04%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

is 'sed' thread safe

How to make a Squid Proxy server?