[Pkg-sysvinit-devel] Bug#907606: fsck takes hours to complete, just due to slow screen output

Harald Dunkel harald.dunkel at aixigo.de
Thu Aug 30 08:01:26 BST 2018

Package: initscripts
Version: 2.88dsf-59.9

In case of an unclean shutdown or system crash fsck run at boot time
can take several hours to complete, printing thousands of useless
messages like

	Clearing orphaned inode 123456789 (uid=1000, gid=1000, mode=0100700, size=28)

It depends of the speed of your console, of course, but using a terminal
it is pretty unlikely that you get anything faster than 115200 bits/sec.
Some VGA consoles are not noticeable faster than this, either.

I had the chance to verify this problem on a master-backup system:

- On the master the fsck is running for >16 hours and is not completed yet.
   It writes to a terminal with 9600 bits/sec.
- On the backup (manually migrated to become the new master) the file
   system check of the same partition took about 30 minutes, using
   "fsck -y >& fsck.log". It wrote 54 MByte logfile.

This could be improved.

Init is sysvinit-core.

Thanx in advance

More information about the Pkg-sysvinit-devel mailing list