Shoutbox

its very much true

and its not a rumour

its a well documented flaw in the ntfs file system

and if you searched the msn help forums you'd find it yourself

sad to say this,. but your very wrong

i and many others have had this error and returning to Fat32 is the only way to fix it

its caused by a mass amount of files being transferred at once, and the way ntfs drives are handled by windows

the bug was introduced in Windows NT SP6 which became windows 2000 and has never been fixed

i suggest you keep your mouth clamped when you yourself haven't researched the bug, and don't transfer the amounts of data i do along my server and within my computer itself

if you want proof

how bout you search google
for

Chkdsk has discovered freespace marked as allocated within the master file table reserved space

and

chkdsk has discovered freespace marked as allocated within the master file table

there is many accounts of the bug, and you will be surprised at how many have blamed everything from windows. to norton systemworks all the way to Nvidia display drivers

the flaw itself lies within the file system and the way the operating system updates the volume bitmap,

which by the way. handles where all the freespace is reported along the drive

this error is not fixable within chkdsk, and even converting back to fat32 and then back to ntfs does not fix it as the error returns very quickly

some people have fixed it using windows update, and those are the lucky ones

i for one don't wish to risk my data becoz of a flaw in a file system that should have been fixed

and word has it that the WINFS has this flaw fixed,

i would suggest not using any file system which indexes all data in one single file as if that file is damaged.. which btw is VERY easy to do,

everything is lost

Fat32 atleast for me. is assured of repairing any errors reported

and one last time

if you get this ntfs and defrag

then you better hope to god that you don't use the windows defragmenter

as it moves files and data into the mft reserved space

once this happens

chkdsk reports that the Master file table os corrupt and begins removing indexes

the only way to fix this is to go back to Fat32 completely

i for one will not be using anying short of Winfs in the future, and even then once i have become certain that this bug is fixed

CookieRevised

i suggest you check up on your info before you post calling my post rumour and nonsense.. especially when you yourself haven't experienced the problem firsthand, and haven't bothered to research the problem itself