Bug#793198: systemd: poweroff, reboot without stopping services and unmounting
Пронин Илья Сергеевич
mimeticdrift at gmail.com
Fri Jul 24 13:41:58 BST 2015
> Can you attach your fstab as well, please.
Sure, did it.
> Which fs errors (for which partitions) do you get exactly. Please copy
> them all verbatim here.
Some of errors from journalctl -a, full log in attach:
8 авг 08 04:02:07 shambler kernel: EXT4-fs error (device sda6):
ext4_mb_generate_buddy:757: group 65, block bitmap and bg
descriptor inconsistent: 2703 vs 2704 fr ee clusters 4089 авг 08
04:02:07 shambler kernel: EXT4-fs error (device sda6):
ext4_mb_generate_buddy:757: group 66, block bitmap and bg
descriptor inconsistent: 12073 vs 12072 free clusters 4090 авг 08
04:02:07 shambler kernel: EXT4-fs error (device sda6):
ext4_mb_generate_buddy:757: group 67, block bitmap and bg
descriptor inconsistent: 22563 vs 22559 free clusters 4091 авг 08
04:02:07 shambler kernel: JBD2: Spotted dirty metadata buffer (dev =
sda6 , blocknr = 0). There's a risk of filesystem corruption in
case of system crash.
июл 24 15:20:42 shambler kernel: EXT4-fs (sda6): error count since
last fsck: 14 4508 июл 24 15:20:42 shambler kernel: EXT4-fs (sda6):
initial error at time 143773796 2: ext4_mb_generate_buddy:757 4509
июл 24 15:20:42 shambler kernel: EXT4-fs (sda6): last error at time
1186531327: ext4_mb_generate_buddy:757
авг 08 04:01:14 shambler systemd-fsck[416]: /dev/sda6 contains a file
system with errors, check forced. 1736 авг 08 04:01:14 shambler
systemd-fsck[375]: /dev/sda8 contains a file system wit h errors,
check forced. 1737 авг 08 04:01:14 shambler
systemd-fsck[375]: /dev/sda8: Inode 13, i_size is 29040 , should
be 35840. FIXED.
> I'm also confused now, when the problem actually happens:
> Does it happen with systemctl reboot, systemctl poweroff, shutdown
> from lxde menu, reboot from lxde menu?
Looks like floating bug. At the moment boots like hell every time,
errors and falling to maintenance mode. That for both systemctl
and LXDE.
Sometimes, I got much less errors or boot absolutely without errors.
I've single core CPU so seems threading in systemd is not a reason.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fstab
Type: application/octet-stream
Size: 2313 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150724/d5afa6ac/attachment-0002.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: err_dmesg.txt
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150724/d5afa6ac/attachment-0004.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: err_journalctl.txt
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150724/d5afa6ac/attachment-0005.txt>
More information about the Pkg-systemd-maintainers
mailing list