RE: NTFS or FAT32 for an external drive?
Any room for a Computer Scientist? Yes? Good.
squall, do you have any idea how a hard drive works? How a filesystem works? How the OS, filesystem and hard disk interact? I've skipped most of your bullshit because you clearly don't understand at all.
For instance, do you know what FAT stands for? In fact, why don't we check your familiarity with FSs in general? So, what's an inode?
I may not have fiddled with hard drives at a low level, but I have written an all-software FAT filesystem, so I know for certain how much you need to overwrite to render the drive useless. How much, do you ask? One entry - the root directory. Overwrite that, and the entire filesystem goes down. Not to mention the complete lack of journalling, which allows small errors to accumulate and cripple the entire partition.
Now, NTFS and its MFT are much more resilient, due mostly to journalling. So, if the root directory is overwritten, the journal can be used to recover it.
As for these CHKDSK errors, you really think they can't be fixed? Free MFT space that's marked as allocated can be remarked as free if that space isn't part of a file. If it is, then you move the data somewhere else, out of the MFT.
Try doing that in FAT32 - you can't.
As for these errors 'proving' that there's a flaw...
(at this point patience expires)
That is absolute bollocks. I'm sorry, but a few people experience an entirely fixable error, and you call it a major flaw?
Microsoft haven't patched the bug since there is no bug!
|