list of filesystems with known issues

[Bill Barry]

Matt Mackall wrote:
> On Tue, 2009-03-03 at 17:10 +0100, Jens.Wulf at sew-eurodrive.de wrote:
>   
>> Hi all,
>>
>> every once in a while someone with a corrupted repo pops up on this list. Sometimes it is because he used hg on a filesystem which has issues. 
>> Searching the bugtracker, wiki and mailing list didn't reveal that
>> much about filesystems which should be avoided, though. Maybe I just
>> didn't use the right keywords, but everything I found was 
>>   "There are known problems with XFS on Linux, but that's about it."
>>
>> Which ones cause problems?
>>     
>
> XFS on Linux: some versions lose writes to revlogs (should be fixed in
> Linux kernels from the past year or so).
>
> NFS on Linux: some versions have attribute caching bugs that
> occasionally cause incorrect output from hg status (again, fixed in
> recent kernels).
>
> We don't have a lot of information about Windows filesystem issues. The
> most frequent problem here tends to be interference by virus scanners.
> The locking and ordering semantics on Windows shares is also possibly
> different, which may allow clients to race when writing to the same
> repository.
>   
There are plenty of problems with windows filesystems:
Two files where the name only differs by case: repo\file.txt and 
repo\file.TXT (you cannot merge a tree where this happens, you cannot 
update to a revision where both files exist, etc.)
Windows filesystem locks suck.
I am willing to bet there are bugs around ADS: 
http://www.forensicfocus.com/dissecting-ntfs-hidden-streams


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090303/13bf13b0/attachment.htm