list of filesystems with known issues

[Matt Mackall]

On Wed, 2009-03-04 at 08:04 +0100, Jens.Wulf at sew-eurodrive.de wrote:
> > 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.
> Are there any reported bugs related to that?
> 
> Statements regarding windows (file)systems are quite vague, but
> suggest to not access a repo concurrently, no matter whether it is a
> network or local filesystem...

We haven't pinned anything on it yet, no. It's not very high on my list
of concerns, but it's a theory I drag out when things behave
mysteriously. Just about all such reports have eventually been pinned on
something else (user error or hardware failure being common).

I do -not- expect to see locking issues on local filesystems. Even the
worst operating systems manage to get atomicity of local file creation
right.

I'd also expect Mercurial to notice if locking on a Windows share ever
went wrong, as one client would find the lock it held missing and
complain. And no one's seen that yet either. But this is much easier for
an operating system to get wrong than the local case and lots of network
filesystems have in fact been lazy here.

Have any symptoms for us?

-- 
http://selenic.com : development and support for Mercurial and Linux