Mark Stosberg <bugs@darcs.net> writes:
> Mark Stosberg <mark@summersault.com> added the comment:
>
>>From what I can tell, "Device or resource busy" comes not from Darcs or
> GHC-land, but from Linux/NFS.
I realize it's NFS-related. Perhaps I should have made clear originally
that I expected it to be known whether it works on NFS generally, though
I couldn't find anything to say so.
> See all the results for here:
>
> https://encrypted.google.com/search?q=nfs++%22Device+or+resource+busy%22
>
> I'm tentatively marking this as "not our bug". If the issue can be
> reproduced in a way that is clearly darcs fault, please re-open it.
Are you saying that darcs simply isn't supported on NFS (or other --
AFS, CIFS, FUSE?) filesystems? If so, it needs documenting.
Looking more closely, and assuming the "rename" message is actually from
rename(2), POSIX says:
[EBUSY]
[CX] [Option Start] The directory named by old or new is currently
in use by the system or another process, and the implementation
considers this an error. [Option End]
and the Debian says:
EBUSY The rename fails because oldpath or newpath is a directory that
is in use by some process (perhaps as current working directory,
or as root directory, or because it was open for reading) or is
in use by the system (for example as mount point), while the
system considers this an error. (Note that there is no require‐
ment to return EBUSY in such cases — there is nothing wrong with
doing the rename anyway — but it is allowed to return EBUSY if
the system cannot otherwise handle such situations.)
which suggests it is darcs' "fault", but if it's not going to be fixed,
it would be useful for people to know they need to use a local
filesystem. (It seems as if that's wise for performance reasons, but
that's a different issue.)
|