#501481 drop logsave from checkroot.sh and checkfs.sh please?

Package:
initscripts
Source:
sysvinit
Submitter:
Harald Dunkel
Date:
2021-01-31 06:33:07 UTC
Severity:
wishlist
Tags:
#501481#5
Date:
2008-10-07 18:14:04 UTC
From:
To:
If I remove the "logsave -s $FSCK_LOGFILE" in checkroot.sh and
checkfs.sh, then my PC boots in 43sec instead of 55sec. Thats an
improvement of about 20% for just 2 partitions (/ and /home).

Filesystem on both partitions is reiserfs.


Would it be possible to make running logsave optional?


Regards

Harri
#501481#10
Date:
2008-10-07 18:28:56 UTC
From:
To:
[Harald Dunkel]

Interesting.

This is actually the calls to fsck, I believe, and it is already
optional if you want to use fsck by modifying /etc/fstab.

What is the content of your /etc/fstab?  I would expect the fsck calls
to be quick if no partition was to be fsck-ed (aka the last number in
/etc/fstab is 0).  Does it work?

Happy hacking,
#501481#15
Date:
2008-10-07 20:10:14 UTC
From:
To:
Petter Reinholdtsen wrote:

I don't want to drop fsck. I just would like to skip the logsave
wrapper. My change to get the 20% speed improvement looke like
this: Instead of

	logsave -s $FSCK_LOGFILE fsck $spinner $force $fix -t $roottype $rootdev
use
	fsck $spinner $force $fix -t $roottype $rootdev


Regards

Harri
#501481#20
Date:
2019-02-21 17:55:10 UTC
From:
To:
control: tags -1 +moreinfo

[2008-10-07 22:10] Harald Dunkel <harald.dunkel@t-online.de>

Hello. Sorry for late response. Is still wanted? By the way, logsave is
nowdays run only if it is installed, since e2fsprogs no longer
essential.
#501481#27
Date:
2019-03-16 15:29:39 UTC
From:
To:
I am running ext4 instead of reiserfs today, but logging fsck has still
a *severe* impact on boot time performance. We have a few Debian file
servers in the office, e.g. providing /home/* via NFS. They are managed
remotely using some serial-over-line technology instead of a vga console.

A few months ago such a server went down without a clean umount. On the
next boot it was busy for >2h to show billions of lines about some tiny
repairs it has performed. Mo end was in sight. Then I gave up, interrupted
fsck, booted the host in single user mode, and rerun fsck writing to a log
file instead of the serial line. It was completed within 15 minutes. No
serious problems.

Regards
Harri
#501481#32
Date:
2019-03-17 11:15:01 UTC
From:
To:
[2019-03-16 16:29] Harald Dunkel <harri@afaics.de>

I see. How fine grained control you need? Do you need separate controls
to enable/disable logsave for `checkroot.sh' and `checkfs.sh'?

I consider two possible implementations for current feature request --
either make FSCK_LOGFILE variable configurable via
/etc/default/{checkfs,checkroot} or add variable `WANT_LOGSAVE' there.
Not sure, which is better. Opinions?

Just in case. Dear submitter, you are aware, that init.d scripts are
conffiles, aren't you?