<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
for information. <br>
<br>
Note the existing bug number<br>
<br>
Cheers<br>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
</th>
<td>xenial: Watch out for boot failures due to /etc/mtab
file</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Thu, 29 Oct 2015 14:43:22 +0100</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Martin Pitt <a class="moz-txt-link-rfc2396E" href="mailto:martin.pitt@ubuntu.com"><martin.pitt@ubuntu.com></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td>Ubuntu Development <a class="moz-txt-link-rfc2396E" href="mailto:ubuntu-devel@lists.ubuntu.com"><ubuntu-devel@lists.ubuntu.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Hello all,
/etc/mtab is supposed to be a symlink to /proc/self/mounts (or
/proc/mounts) for stuff to work. We've also shipped
"debian-fixup.service" since vivid to turn a file into a symlink on
boot.
However, if you have /etc/mtab as a file (e. g. right after
installation), current xenial's systemd will fail hard to boot with
something like
| systemd [1]: /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please replace /etc/mtab with a symlink to /proc/self/mounts.
| systemd [1]: Freezing execution.
This is of course a really harsh failure mode, and it will be changed
again in a few weeks or so to merely warn about that. But as these
warnings have existed for a long time already, and nobody notices
them, having this hard failure mode will actually tell us which places
we need to fix. E. g. a week ago debian-installer was fixed [1], and I
just heared on IRC that a Xubuntu desktop install fails as well; bug
was just filed [2].
We really must stop writing /etc/mtab files. It breaks libmount's
monitoring and all kinds of old school software which still reads
/etc/mtab directly; ideally they should of course be fixed to look
into /proc, and /etc/mtab should just die, but there's still some way
to go (e. g. [3]).
So for now, if you see a boot failure like this, please report it and
ping me, so that we can fix our installers, images etc. to not produce
a broken /etc/mtab any more. After that, just remove /etc/mtab (e. g.
temporarily boot with upstart) to resume.
After we fixed our installers (ubiquity, d-i, cloud-init, etc.), we'll
go back to warning (IOW: ignore) mode.
Thanks,
Martin
[1] <a class="moz-txt-link-freetext" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802187">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802187</a>
[2] <a class="moz-txt-link-freetext" href="https://launchpad.net/bugs/1511376">https://launchpad.net/bugs/1511376</a>
[3] <a class="moz-txt-link-freetext" href="https://sourceware.org/bugzilla/show_bug.cgi?id=19108">https://sourceware.org/bugzilla/show_bug.cgi?id=19108</a>
--
Martin Pitt | <a class="moz-txt-link-freetext" href="http://www.piware.de">http://www.piware.de</a>
Ubuntu Developer (<a class="moz-txt-link-abbreviated" href="http://www.ubuntu.com">www.ubuntu.com</a>) | Debian Developer (<a class="moz-txt-link-abbreviated" href="http://www.debian.org">www.debian.org</a>)
</pre>
<br>
</div>
<br>
</body>
</html>