Quote Originally Posted by kl522 View Post
I keep telling you but not sure if you got my point, I am not saying NTFS is not unmounted cleanly. I am saying knoppix-data.xxx which is a loop mounted ext2/ext3 file system sitted on NTFS which is not unmounted cleanly.
Yes, I get it - what I was saying is, I have the same filesystems, and it doesn't appear to have difficulty unmounting cleanly on shutdown. If I have to kill it, like when Hulu, or any Flash video is maxing out the processor to do the NTFS filesystem stuff (complicated to obfuscate, thanks so much Mr. Gates!) then I notice it takes a little longer to boot up afterwards.
And you won't even notice it !!! Unless you have some means to check it offline, otherwise the only exhibits it gives is slower boot time, because the knoppix minirt.gz contains code which automatically perform e2fsck on the knoppix-data.xxx !

( As a side-track, even if NTFS is not cleanly removed from the mounts, you also will not know it. I have seen many cases where I poweroff NTFS in Linux, the system will still come back without needing a file system check. )
Sorry to bore you with more information. As I did more and more testings, I found that this problem is not limited to hosting knoppix-data.img on NTFS. As I perform more tests, I found that this problem happens to almost all kinds of file systems which hosting the loop mounted knoppix-data.img, ie it also happens to ext2/ext3 and VFAT. The tendency of this to happen are :-

1. The knoppix-data.xxx must be big ( in my case it is 2.5 G ).
2. There were some file system activities prior to shutdown ( such as you have saved some files to knoppix home directory ).
3. Maybe the machine need to have huge memory ( > 1 G ).

You notice that after you shutdown/poweroff the system, the knoppix-data.img ( ie the /KNOPPIX-DATA directory ) was not unmounted cleanly.
What's the best way to see that? I imagine re-booting without mounting knoppix-data might be necessary, but what else do you do?
Most of you do not notice this, as I mentioned before, it is because knoppix minirt.gz has e2fsck inside it. But as with any uncleanly detached file systems, there might be corruption or unsaved data.
Thanks for doing all that testing!

Cheers!