Saucy: /forcefsck not being removed after execution / completion of boot system check

[Phil Wyett]

'/forcefsck' not being removed after execution / completion of boot system check.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: e2fsprogs 1.42.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Tue Sep 24 10:12:13 2013
InstallationDate: Installed on 2013-09-12 (12 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: e2fsprogs
UpgradeStatus: Upgraded to saucy on 2013-09-12 (12 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Theodore Ts'o (tytso)]

It's not e2fsprogs' responsibility to remove the /forcefsck file. It is the job of initscripts.

[Ken Sharp (kennybobs)]

Seeing this in Precise today. Never used to occur.

[Steve Langasek (vorlon)]

This has been assigned to mountall, but mountall has:

post-stop script
    rm -f /forcefsck 2>dev/null || true
end script

And that's been in place since mountall was first introduced in Ubuntu.

So if this isn't working for you, we'll need some help understanding why.

[Ken Sharp (kennybobs)]

Saucy and Precise are EOL and this seems to work in later releases.