Bug#808884: filesystem check progress messages to boot console always remain at 0.0% if more than one filesystem is being checked

[Michael Biebl]

Control: tags -1 moreinfo

On Thu, 24 Dec 2015 10:52:16 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
 wrote:
> Package: systemd
> Version: 228-2+b1
> Severity: minor
> 
> If there are any "(checking 2 filesystems)" type messages to the console
> upon boot, the progress will always just show 0.0%.
> 
> checking one filesystem messages work fine, but if it is checking more
> than one, then progress percentages stay at 0.0% though indeed after a
> minute the check still completes.

Seems to work fine here (using 232-15).

Can you still reproduce the problem with an up-to-date version?
What file system is that? Does the fsck utility for that file system
provide progress information?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#808884: filesystem check progress messages to boot console always remain at 0.0% if more than one filesystem is being checked

[積丹尼 Dan Jacobson]

Package: systemd
Version: 228-2+b1
Severity: minor

If there are any "(checking 2 filesystems)" type messages to the console
upon boot, the progress will always just show 0.0%.

checking one filesystem messages work fine, but if it is checking more
than one, then progress percentages stay at 0.0% though indeed after a
minute the check still completes.


# journalctl |grep check\ forced
12月 24 10:39:06 jidanni2 systemd-fsck[368]: /dev/sda7 has been mounted 21 times 
without being checked, check forced.
12月 24 10:40:35 jidanni2 systemd-fsck[373]: /dev/sda6 has been mounted 35 times 
without being checked, check forced.


12月 24 10:39:04 jidanni2 systemdstemd[1]: Found device FUJITSU_MHT2040AT 12.
12月 24 10:39:04 jidanni2 systemd[1]: Found device FUJITSU_MHT2040AT 7.
12月 24 10:39:04 jidanni2 systemd[1]: Starting File System Check on 
/dev/disk/by-uuid/34610b6a-70a3-48d9-b135-9
6907dc2ba16...
12月 24 10:39:04 jidanni2 systemd[1]: Activating swap 
/dev/disk/by-uuid/ce5499e2-019e-44cc-8f95-d027832b3d7d...
12月 24 10:39:04 jidanni2 systemd[1]: Reached target Sound Card.
12月 24 10:39:04 jidanni2 systemd[1]: Listening on Load/Save RF Kill Switch 
Status /dev/rfkill Watch.
12月 24 10:39:05 jidanni2 kernel: Adding 997884k swap on /dev/sda12.  
Priority:-1 extents:1 across:997884k FS
12月 24 10:39:05 jidanni2 systemd[1]: Activated swap 
/dev/disk/by-uuid/ce5499e2-019e-44cc-8f95-d027832b3d7d.
12月 24 10:39:05 jidanni2 systemd[1]: Reached target Swap.
12月 24 10:39:06 jidanni2 systemd-fsck[368]: /dev/sda7 has been mounted 21 times 
without being checked, check f
orced.
12月 24 10:39:06 jidanni2 systemd[1]: Found device FUJITSU_MHT2040AT 6.
12月 24 10:39:06 jidanni2 systemd[1]: Starting File System Check on 
/dev/disk/by-uuid/355d426a-cbfc-4faf-91d6-4
f9405199517...
12月 24 10:39:09 jidanni2 systemd-udevd[335]: Process '/usr/sbin/alsactl -E 
HOME=/var/run/alsa restore 1' faile
d with exit code 99.
12月 24 10:39:09 jidanni2 systemd-udevd[330]: Process '/usr/sbin/alsactl -E 
HOME=/var/run/alsa restore 29' fail
ed with exit code 99.
12月 24 10:39:09 jidanni2 systemd-udevd[334]: Process '/usr/sbin/alsactl -E 
HOME=/var/run/alsa restore 0' faile
d with exit code 99.
12月 24 10:40:35 jidanni2 systemd-fsck[368]: /dev/sda7: 13217/678912 files 
(11.4% non-contiguous), 2570599/5428
048 blocks
12月 24 10:40:35 jidanni2 systemd[1]: Started File System Check on
/dev/disk/by-uuid/34610b6a-70a3
...

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers