Systemd generated mount file is not deleted when the mount point entry in fstab is deleted or modified
Clash Royale CLAN TAG#URR8PPP
I recently started using systemd in linux. On systemd mount, I have some observations:
- mount unit file is generated with mount point name when there is an entry in /etc/fstab.
I also observed the two scenarios listed below:
Precondition: I have below entry in fstab:
/dev/sda3 /test_mount ext4 rw,acl,nobarrier,nodelalloc 0 0
(So test_mount.mount file is generated under /var/run/systemd/generator/ directory after reboot.)
Scenario 1: I deleted the entry from fstab and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory. But the file is not deleted and systemd is attempting to mount the device node.
Scenario 2: I modified the entry in fstab. I renamed the mountpoint to sec_test_mount and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory and sec_test_mount.mount file should be newly created. sec_test_mount.mount is newly created but test_mount.mount is not deleted. Both the mount files are trying to mount and mount has happened twice.
debian mount systemd fstab
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
add a comment |
I recently started using systemd in linux. On systemd mount, I have some observations:
- mount unit file is generated with mount point name when there is an entry in /etc/fstab.
I also observed the two scenarios listed below:
Precondition: I have below entry in fstab:
/dev/sda3 /test_mount ext4 rw,acl,nobarrier,nodelalloc 0 0
(So test_mount.mount file is generated under /var/run/systemd/generator/ directory after reboot.)
Scenario 1: I deleted the entry from fstab and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory. But the file is not deleted and systemd is attempting to mount the device node.
Scenario 2: I modified the entry in fstab. I renamed the mountpoint to sec_test_mount and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory and sec_test_mount.mount file should be newly created. sec_test_mount.mount is newly created but test_mount.mount is not deleted. Both the mount files are trying to mount and mount has happened twice.
debian mount systemd fstab
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
add a comment |
I recently started using systemd in linux. On systemd mount, I have some observations:
- mount unit file is generated with mount point name when there is an entry in /etc/fstab.
I also observed the two scenarios listed below:
Precondition: I have below entry in fstab:
/dev/sda3 /test_mount ext4 rw,acl,nobarrier,nodelalloc 0 0
(So test_mount.mount file is generated under /var/run/systemd/generator/ directory after reboot.)
Scenario 1: I deleted the entry from fstab and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory. But the file is not deleted and systemd is attempting to mount the device node.
Scenario 2: I modified the entry in fstab. I renamed the mountpoint to sec_test_mount and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory and sec_test_mount.mount file should be newly created. sec_test_mount.mount is newly created but test_mount.mount is not deleted. Both the mount files are trying to mount and mount has happened twice.
debian mount systemd fstab
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
I recently started using systemd in linux. On systemd mount, I have some observations:
- mount unit file is generated with mount point name when there is an entry in /etc/fstab.
I also observed the two scenarios listed below:
Precondition: I have below entry in fstab:
/dev/sda3 /test_mount ext4 rw,acl,nobarrier,nodelalloc 0 0
(So test_mount.mount file is generated under /var/run/systemd/generator/ directory after reboot.)
Scenario 1: I deleted the entry from fstab and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory. But the file is not deleted and systemd is attempting to mount the device node.
Scenario 2: I modified the entry in fstab. I renamed the mountpoint to sec_test_mount and rebooted the machine. My expectation is test_mount.mount file should be deleted from /var/run/systemd/generator/ directory and sec_test_mount.mount file should be newly created. sec_test_mount.mount is newly created but test_mount.mount is not deleted. Both the mount files are trying to mount and mount has happened twice.
debian mount systemd fstab
debian mount systemd fstab
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
edited Feb 7 at 7:21
Rui F Ribeiro
40.7k1479137
40.7k1479137
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
asked Feb 7 at 1:37
Arulananth SubramaniamArulananth Subramaniam
132
132
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
systemd-fstab-generator creates the mount units under /run, because that filesystem is a tmpfs (in-memory filesystem), which is not preserved across reboots, so it's expected to be replaced with an empty volume on every boot.
(/var/run is supposed to be a symlink to /run, which is the tmpfs mount. That name exists for compatibility only, modern Linux uses /run directly everywhere.)
If that is not the case on your machine, I'd say that is where the problem is... If you fix that, the generator will properly recreate the mount units on every boot, since the tmpfs will be empty each time.
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
@filbrandenThank you very much for your reply./var/runis symlink to/runbut/runis not tmpfs mount in my system.
– Arulananth Subramaniam
Feb 8 at 2:24
I believe systemd will always mount/runautomatically, so not sure why that is not happening correctly in your case... If you have an entry for/runin fstab, try removing that and rebooting to see if/runis now mounted correctly. Good luck!
– filbranden
Feb 8 at 4:11
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f499201%2fsystemd-generated-mount-file-is-not-deleted-when-the-mount-point-entry-in-fstab%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
systemd-fstab-generator creates the mount units under /run, because that filesystem is a tmpfs (in-memory filesystem), which is not preserved across reboots, so it's expected to be replaced with an empty volume on every boot.
(/var/run is supposed to be a symlink to /run, which is the tmpfs mount. That name exists for compatibility only, modern Linux uses /run directly everywhere.)
If that is not the case on your machine, I'd say that is where the problem is... If you fix that, the generator will properly recreate the mount units on every boot, since the tmpfs will be empty each time.
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
@filbrandenThank you very much for your reply./var/runis symlink to/runbut/runis not tmpfs mount in my system.
– Arulananth Subramaniam
Feb 8 at 2:24
I believe systemd will always mount/runautomatically, so not sure why that is not happening correctly in your case... If you have an entry for/runin fstab, try removing that and rebooting to see if/runis now mounted correctly. Good luck!
– filbranden
Feb 8 at 4:11
add a comment |
systemd-fstab-generator creates the mount units under /run, because that filesystem is a tmpfs (in-memory filesystem), which is not preserved across reboots, so it's expected to be replaced with an empty volume on every boot.
(/var/run is supposed to be a symlink to /run, which is the tmpfs mount. That name exists for compatibility only, modern Linux uses /run directly everywhere.)
If that is not the case on your machine, I'd say that is where the problem is... If you fix that, the generator will properly recreate the mount units on every boot, since the tmpfs will be empty each time.
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
@filbrandenThank you very much for your reply./var/runis symlink to/runbut/runis not tmpfs mount in my system.
– Arulananth Subramaniam
Feb 8 at 2:24
I believe systemd will always mount/runautomatically, so not sure why that is not happening correctly in your case... If you have an entry for/runin fstab, try removing that and rebooting to see if/runis now mounted correctly. Good luck!
– filbranden
Feb 8 at 4:11
add a comment |
systemd-fstab-generator creates the mount units under /run, because that filesystem is a tmpfs (in-memory filesystem), which is not preserved across reboots, so it's expected to be replaced with an empty volume on every boot.
(/var/run is supposed to be a symlink to /run, which is the tmpfs mount. That name exists for compatibility only, modern Linux uses /run directly everywhere.)
If that is not the case on your machine, I'd say that is where the problem is... If you fix that, the generator will properly recreate the mount units on every boot, since the tmpfs will be empty each time.
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
systemd-fstab-generator creates the mount units under /run, because that filesystem is a tmpfs (in-memory filesystem), which is not preserved across reboots, so it's expected to be replaced with an empty volume on every boot.
(/var/run is supposed to be a symlink to /run, which is the tmpfs mount. That name exists for compatibility only, modern Linux uses /run directly everywhere.)
If that is not the case on your machine, I'd say that is where the problem is... If you fix that, the generator will properly recreate the mount units on every boot, since the tmpfs will be empty each time.
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
answered Feb 7 at 13:56
filbrandenfilbranden
9,98621645
9,98621645
@filbrandenThank you very much for your reply./var/runis symlink to/runbut/runis not tmpfs mount in my system.
– Arulananth Subramaniam
Feb 8 at 2:24
I believe systemd will always mount/runautomatically, so not sure why that is not happening correctly in your case... If you have an entry for/runin fstab, try removing that and rebooting to see if/runis now mounted correctly. Good luck!
– filbranden
Feb 8 at 4:11
add a comment |
@filbrandenThank you very much for your reply./var/runis symlink to/runbut/runis not tmpfs mount in my system.
– Arulananth Subramaniam
Feb 8 at 2:24
I believe systemd will always mount/runautomatically, so not sure why that is not happening correctly in your case... If you have an entry for/runin fstab, try removing that and rebooting to see if/runis now mounted correctly. Good luck!
– filbranden
Feb 8 at 4:11
@filbranden Thank you very much for your reply. /var/run is symlink to /run but /run is not tmpfs mount in my system.– Arulananth Subramaniam
Feb 8 at 2:24
@filbranden Thank you very much for your reply. /var/run is symlink to /run but /run is not tmpfs mount in my system.– Arulananth Subramaniam
Feb 8 at 2:24
I believe systemd will always mount
/run automatically, so not sure why that is not happening correctly in your case... If you have an entry for /run in fstab, try removing that and rebooting to see if /run is now mounted correctly. Good luck!– filbranden
Feb 8 at 4:11
I believe systemd will always mount
/run automatically, so not sure why that is not happening correctly in your case... If you have an entry for /run in fstab, try removing that and rebooting to see if /run is now mounted correctly. Good luck!– filbranden
Feb 8 at 4:11
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f499201%2fsystemd-generated-mount-file-is-not-deleted-when-the-mount-point-entry-in-fstab%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
