Description of problem: I'm building a diskless cluster based on mageia3. Everything is done and systems boots NFS via DHCP/PXE. However, if the filesystem is exported 'read-only', systemd will fail causing an abort, and freeze. ---- mageia 3 [failed] systemd - Inserting module autofs4 // I don't care. I'm not using autofs. [OK] systemd - sethostname to localhost [OK] systemd - Initializing machine ID from random generator [failed] systemd - Assertion 'close_nointr(fd) == 0' failed at src/shared/util.c:313 function close_nointr_nofail(). Aborting. [failed] systemd - Caught <ABRT>. core dump failed [failed] systemd - Freezing Execution. -------- At that point the cluster node is locked up. If the filesystem is exported 'rw' it boots without error. Now the odd part. If the filesystem is re-exported 'ro' (exportfs -r), systemd will instantly print on the cluster node console; systemd-journald[XXXX]: Assertion 'close_nointr(fd) == 0' failed at src/shared/util.c:313, function close_nointr_nofail(). Aborting. It will repeat this a batches of 4, every minute. This time it is not fatal. Version-Release number of selected component (if applicable): Mageia3 3.8.13-server-1.mga3 How reproducible: Very Steps to Reproduce: 1. This is for a nfs diskless cluster with read-only rootfs. Please see forum discussion: 2. https://forums.mageia.org/en/viewtopic.php?f=8&t=5509 3. Reproducible: Steps to Reproduce:
CC: (none) => mageia
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD