[clue] NTFS logical structure corruption?

[Bruce Ediger]

On Wed, 7 Mar 2012, David L. Willson wrote:

> 1) Use CHKDSK to repair the filesystem
> 2) Use TAKEOWN to ...
> 3) Use ICACLS to ...

I thought about this for a while, and I worry about being contentious
or whatever, so feel free to slap me down for this...

I also may be showing my age.  In 1993-94, when NT first came out, the
Windows advocates were all saying that NTFS would never require the
moral eqivalent of a "fsck", because of the great design of NTFS.

Although I've been an at-work Windows user for 8 years now, I've never
really experienced an NTFS oddity that required a CHKDSK (which is the
moral equivalent of "fsck", right?).

On the other hand, I've never since 1988 had a Unix or NetBSD or Linux
filesystem not easily fixable by "fsck -p", except when the disk drive
died with audible scraping noises and thunks.

Why does NTFS need the elaborate fix procedure you show above?  And why
is NTFS so "magical" that alternate (linux) tools can't fix it?  The
NetBSD folks were able to modify UFS to become ext2fs fairly readily,
and at least a couple of Linux reverse-engineered NTFS implementations
exist, right?