no matter how you initiate fsck, be it by 'touch /forcefsck'' or by manually increasing mount count by 'tune2fs -C <no>' fsckk either silently aborts or with latest kernel update to 2.6.32-20 interrupst boot process ending with a dead system.
Checked with root filesystems ext3 and ext4.
no matter how you initiate fsck, be it by 'touch /forcefsck'' or by manually increasing mount count by 'tune2fs -C <no>' fsckk either silently aborts or with latest kernel update to 2.6.32-20 interrupst boot process ending with a dead system.
Checked with root filesystems ext3 and ext4.
Se also https:/ /bugs.launchpad .net/bugs/ 538810 which dates back 1 month.