I've uploaded test packages to
https://people.debian.org/~biebl/systemd/stretch/
You can install them by first installing apt-transport-https, then
adding to your sources.list:
deb [trusted=yes] https://people.debian.org/~biebl/systemd/stretch/ ./
Please report back if those packages fix your
On Sat, Feb 11 2017, Michael Biebl wrote:
>> I cannot explain why given the exact same partition/volume scheme by
>> lvm/cryptsetup, in one case I can shutdown cleanly, and in the other it
>> breaks.
>
> While I can reproduce the error messages on shutdown, it does *not*
> cause a dirty file system
Am 11.02.2017 um 16:21 schrieb Yuri D'Elia:
> On Sat, Feb 11 2017, Michael Biebl wrote:
>>> reached? If I cannot get a clean journal out, there's nothing much I can
>>> debug.
>>
>> You could try to attach a serial device to your VM and log the output to
>> that device [1]. This will get us a more
On Sat, Feb 11 2017, Michael Biebl wrote:
>> reached? If I cannot get a clean journal out, there's nothing much I can
>> debug.
>
> You could try to attach a serial device to your VM and log the output to
> that device [1]. This will get us a more complete log.
> Attach the complete file.
But for
Am 11.02.2017 um 14:38 schrieb Yuri D'Elia:
> reached? If I cannot get a clean journal out, there's nothing much I can
> debug.
You could try to attach a serial device to your VM and log the output to
that device [1]. This will get us a more complete log.
Attach the complete file.
[1] https://fr
On Sat, Feb 11 2017, Michael Biebl wrote:
> While I can reproduce the error messages on shutdown, it does *not*
> cause a dirty file system (in particular /var) here.
> I do have persistent journal enabled on the test VM, but the filing
> killing/unmount spree in systemd-shutdown properly unmounts
Am 10.02.2017 um 12:14 schrieb Yuri D'Elia:
> On Fri, Feb 10 2017, Michael Biebl wrote:
>> Looks similar to
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848044 and a lot like
>> https://github.com/systemd/systemd/issues/1620
>
> Uhm, it does. Aside from the fact that it's not at all harmle
On Fri, Feb 10 2017, Michael Biebl wrote:
> Looks similar to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848044 and a lot like
> https://github.com/systemd/systemd/issues/1620
Uhm, it does. Aside from the fact that it's not at all harmless as
mentioned, since the root fs is not unmounted.
Am 09.02.2017 um 16:39 schrieb Yuri D'Elia:
> Package: systemd
> Version: 232-15
> Severity: normal
>
> I've setup a VM using kvm with a virtio block device, running debian
> unstable
> and an encrypted root filesystem (automatically setup during
> installation as
> lvm+encrypted volume).
>
> Som
Package: systemd
Version: 232-15
Severity: normal
I've setup a VM using kvm with a virtio block device, running debian unstable
and an encrypted root filesystem (automatically setup during installation as
lvm+encrypted volume).
Somehow, systemd tries to stop the lvm/crypto block devices way too
10 matches
Mail list logo
