Bug#777735: systemd: Disk corruption on reboot initiated through systemd
biebl at debian.org
Thu Feb 12 07:50:59 GMT 2015
Am 12.02.2015 um 08:31 schrieb Michael Biebl:
> Am 12.02.2015 um 07:34 schrieb Michael Biebl:
>> Am 12.02.2015 um 07:29 schrieb Peter Colberg:
>>> On Thu, Feb 12, 2015 at 07:14:05AM +0100, Michael Biebl wrote:
>>> It is curious that the bug only manifests itself with the qemu watchdog.
>>> Two physical machines using the hardware iTCO_wdt watchdog reboot fine.
>> In my tests, I did indeed have an unclean shutdown, and got an fsck on
>> next boot. Which looks to me, as if the watchdog i.e. qemu resets the VM
>> before it can shutdown cleanly.
> A "systemctl poweroff" does not seem to trigger this issue. In that
> case, the system is properly shutdown.
> Only on "systemctl reboot" I'm to reproduce the problem, that the VM is
> reset after having reached the shutdown target.
> With poweroff it looks like this (dump from the serial console log)
> Note this line:
> [ 9.402243] i6300esb: Unexpected close, not stopping watchdog!
Some more findings: Aside from only happening on reboot, but not
shutdown, it also seems to only happen with i6300esb. Switching the qemu
config to use ib700 instead of i6300esb, I am not able to trigger the
problem. This confirm's Peter's findings who was not able to reproduce
it on real hardware.
I wonder, if this is a qemu issue, after all?
CCing our Debian qemu maintainer. Maybe he has some insight on this
matter (the complete bug log is at ).
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers