On Aug 9, 2009, at 12:40 PM, Matthias Teege wrote: > Moin, > > I have a small project on an AFS file system. I fossil commit gives > me an > disk I/O error. > > New_Version: 810d89fcb62d6821cd20e6b6b25b0bb112370b2c > fossil: disk I/O error > COMMIT > > There are also two new files, manifest and manifest.uuid in the > directory. > I think the checkin is ok but the disk i/o error makes me nervous. > > I use "This is fossil version [e00a5de0f1] 2009-08-01 14:34:24 UTC" > under > Linux. > > Does anyone use fossil on AFS? How do I get rid of this error?
My guess is that this has something to do with AFS not supporting posix advisory locks. As currently implemented, fossil requires posix advisory locks to work - in order to maintain file consistency if two or more processes try to modify the same repository at the same time. I don't know of an easy work-around at the moment (other than for you to switch to a file system that actually supports unix file semantics correctly.) I'll have to cook something up. > > Many thanks > Matthias > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
