Re: Corrupted file names

Greg Troxel <[email protected]>
Newsgroups gmane.network.unison.general
Message-ID <[email protected]>
John Rose <[email protected]> writes:

> So I went into Windows and ran chkdisk and found that there was indeed
> and index problem with the above file. Once fixed everything syncs
> OK. I am not sure whether this file corruption problem happened at the
> same time as the similar ones reported on 20 February or later.

Thanks for continuing to look into this and figure out more about what
happened.

It is basically a 100% conclusion that user programs cannot cause file
system inconsistencies.

> Quite disturbing and annoying, still no clear idea about why it
> happened and what to do? Even if there is no direct incrimination of
> unison, perhaps it is possible that the high volume IO is enough to
> push the Ubuntu management of ntfs beyond its limit? I will post
> further news if the problem continues.


I think it is plausible that high-volume IO is troublesome while low
loads are not.  Any simllar sync program will neessarily call stat(2) on
efery file, and when actually syncing will read and write a lot.

My only thought (other than "Don't use windows at all." :-) is that
there must be filesystem exerciser/tester programs that do a large
number of operations, from multiple threads, and check the results.
You might find and run such a tool.

Greg

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.