[systemd-devel] Swap gets activated twice (through fstab and gpt generators)

[Lennart Poettering]

On Wed, 28.01.15 13:41, Martin Pitt (martin.pitt at ubuntu.com) wrote:

> Lennart Poettering [2015-01-28 13:15 +0100]:
> > > I built a package with this for Debian and Ubuntu. The Debian reporter
> > > in https://bugs.debian.org/772182 confirmed that this is working, I
> > > think/hope the Ubuntu reporter in
> > > https://bugs.launchpad.net/bugs/1399595 is also usually very
> > > responsive, I think he'll report back soon too. So it fixes that
> > > problem, thanks!
> > 
> > Is the swap device mounted afterwards?
> 
> Yes, and we also confirmed that it's from the fstab generator, not the
> gpt one.
> 
> > > However, in my VM with no GPT, but a simple fstab entry for the swap
> > > booting now hangs forever, swap.target doesn't become active any more.
> > > I don't have time right now to investigate this further, but I suppose
> > > this should be fairly easy to reproduce.
> > 
> > Hmm. Any chance you can boot this in debug mode and get me the last
> > 100 log lines or so when this hangs? Also, could you enable the debug
> > shell and get me the output of "systemctl list-jobs"?
> 
> Both at http://people.canonical.com/~pitti/tmp/systemd-debug/

Ah, thanks! That was helpful.

I apparently fucked up the new linked list iteration macro I added for
this. I think this should make it work:

http://cgit.freedesktop.org/systemd/systemd/commit/?id=cdda4aa8d20c2679cc937d40e793abe7806f17cb

Can you check?

Lennart

-- 
Lennart Poettering, Red Hat