Bug: no fsck on encrypted persistent home directory

[tjacobs]

The boot script doesn't seem to contain support for automatically running fsck on a persistent home at boot time. This can lead to corruption if a persistent home directory is not unmounted cleanly. Currently, the boot actions are as follows:

1. scan devices such as USB keydrives (e.g. /dev/sda1) for filesystems containing knoppix.img
2. mount partition containing knoppix.img
3. map knoppix.img to a loopback device
4. mount the loopback device on /home/knoppix

The problem, of course, is that one or both of the devices (i.e. /dev/sda1 or /dev/loop0) may need an fsck, but this isn't handled at present. The boot script should check both the host drive and the loopback file before mounting.

Is there an official bug tracker where I can report this?

[kelmo]

Do you have a fix or patch to remedy this?