Alpine fails to fsck the root file-system
I am running Alpine 3.6.2 on a Thinkpad T430. There are separate partitions for /boot (ext2), /home (ext4) and / (ext4). The two ext4 file-systems are set up without journals. I just attempted to back up this system with Clonezilla, which complained that the root file-system needed fsck-ing. I don’t recall this system being shut down improperly, so that may be an additional issue. In any case, I then rebooted Alpine, which did not fsck the root file-system. I shut it down and booted another Linux install system (I happened to use Slackware 14.2) and fsck-ed the root file-system, which turned up a number of errors that were corrected.
The problem I’m reporting here is that Alpine did not fsck a file-system that clearly needed it. I’m also wondering how the file-system got into that condition, as I said before, since I am quite sure that the system had never been shut down improperly (is the shutdown process properly sync-ing/umounting the root file-system?).
(from redmine: issue id 7524, created on 2017-07-13)
- Revision 06300dd48343364aee4136dd6dd36e251188e8b8 by Natanael Copa on 2017-07-25T08:47:06Z:
setup-disk: set passno in fstab so filesystems are fsck'ed ref #7524