Bug#780261: fsck scan of crypto-root on EVERY startup

2015-03-27 Thread Holger Todorowski
On Wed, 11 Mar 2015 19:58:23 +0100 Eduard Bloch e...@gmx.de wrote: [...] * Ben Hutchings [Wed, Mar 11 2015, 05:01:58PM]: [...] From the NEWS file: * If the RTC (real time clock) is set to local time and the local time is ahead of UTC, e2fsck will print a warning during boot about

Bug#780261: fsck scan of crypto-root on EVERY startup

2015-03-12 Thread Ben Hutchings
Control: tag -1 - moreinfo Control: reassign -1 e2fsprogs Control: forcemerge 767040 -1 Control: severity 767040 serious On Wed, 2015-03-11 at 19:58 +0100, Eduard Bloch wrote: Hallo, * Ben Hutchings [Wed, Mar 11 2015, 05:01:58PM]: Control: tag -1 moreinfo On Wed, 2015-03-11 at 11:40

Bug#780261: fsck scan of crypto-root on EVERY startup

2015-03-11 Thread Ben Hutchings
Control: tag -1 moreinfo On Wed, 2015-03-11 at 11:40 +0100, Eduard Bloch wrote: Package: initramfs-tools Version: 0.119 Severity: important Just what the topic says. I have encrypted root and plymouth and the bios clock runs in local time. And on every boot, fsck scans the rootfs in

Bug#780261: fsck scan of crypto-root on EVERY startup

2015-03-11 Thread Eduard Bloch
Hallo, * Ben Hutchings [Wed, Mar 11 2015, 05:01:58PM]: Control: tag -1 moreinfo On Wed, 2015-03-11 at 11:40 +0100, Eduard Bloch wrote: Package: initramfs-tools Version: 0.119 Severity: important Just what the topic says. I have encrypted root and plymouth and the bios clock runs

Bug#780261: fsck scan of crypto-root on EVERY startup

2015-03-11 Thread Eduard Bloch
Package: initramfs-tools Version: 0.119 Severity: important Just what the topic says. I have encrypted root and plymouth and the bios clock runs in local time. And on every boot, fsck scans the rootfs in forced mode which takes a while. This started happening only after dist-upgrading today, and