Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab
Duncan Hare
dh at synoia.com
Thu Nov 16 03:52:23 GMT 2017
Michael
sudo mount -o remount,rw
nfs remote share not in 'host.dir' format
It appears /dev/nfs is an exception to everything. But it works.
I suspect the kernel is somewhat difficult about having its root file system remounted under itself.
I have not looked at the kernel code.
Duncan Hare
714 931 7952
From: Michael Biebl <biebl at debian.org>
To: Duncan Hare <dh at synoia.com>; 881834 <881834 at bugs.debian.org>
Sent: Wednesday, November 15, 2017 10:55 AM
Subject: Re: Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab
Please always CC the bug report on replies.
Am 15.11.2017 um 19:26 schrieb Duncan Hare:
> Michael
>
> Thank you for your quick response.
>
> Should be:
>
> The failure results the the root file system being mounted read-only,
> and the system is unusable, because the file system is mounted read only.
>
> Yes, I can log in.
>
> verbose debug log from the boot process: see attached file "journalctl.log "
>
> Please also include the output of the following commands:
> systemctl status systemd-remount-fs : attached file "remount-fs.log"
> sytemd-analyze dump: attached file "systemd.dump"
The journal log indicates that you did not actually use
systemd.log_level=debug to generate a debug log. Please add that to the
kernel command line to get a more verbose log.
That said, why do you have / in /etc/fstab in the first place?
What happens if you remove that fstab entry?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20171116/577d87e9/attachment-0002.html>
More information about the Pkg-systemd-maintainers
mailing list