(assigning to droundy hoping he will reassign to the right person, since I
 don't know who that would be... this isn't important enough for him to fix
 personally)

In CheckFileSystem.lhs, the function can_I_remove_directories_holding_open_files 
opens a file, removes it, then attempts to remove the directory in which that 
file resides.

This will fail on AFS (AFS semantics: when an open file is removed, its inode is 
reattached to the directory as .__afsXXXX until the file is closed ==> hence the 
directory is no longer empty and cannot be removed).  That's no big deal; it 
just means darcs can't use mmap.  But the check function should close the open 
file and then [try to] remove the directory again in order to not leave behind 
droppings.

This manifests itself when you "darcs get" to a destination in /afs/.  Otherwise 
everything works wonderfully.

Thanks!

  - a

My error, this is actually a bug in OpenAFS on certain platforms.

  http://www.openafs.org/pipermail/openafs-info/2006-October/023804.html

If you delete a file while it's open, a phantom file is created.  However, the 
bug causes OpenAFS to forget to delete this phantom file.  I will work with the 
OpenAFS people to get them to fix this.

Sorry to bother y'all.

  - a