Comment 1 for bug 19620

Just some clarification. Ntfsresize doesn't exit uncleanly and doesn't corrupt
NTFS however its extensive __diagnostics__, prior resizing, can find even such
NTFS inconsistencies with which Windows is happily running -- until some bad
thing may happen.

If this is the case then ntfsresize exits with a verbose diagnostic message
instructing the user how to repair his/her already corrupted filesystem.
Otherwise resizing a corrupted filesytem could easy end up permanent data loss.

BTW, since quite many users are confused by the diagnostic messages (the Windows
NTFS driver could be better quality) hence I'm carefully adding support to
ntfsresize thus it's able to repair more type of NTFS damages on-the-fly during
resizing (basically by extending the already built-in mini-ntfsck).