Thus said "Andy Bradford" on 18 Apr 2014 18:56:09 -0600:

> Everything works as expected (e.g. no locking issues).

I spoke too soon.  If I give the Fossil user permissions (e.g. don't 
clone as nobody) then the issue arises again.  

It  doesn't appear  to be  isolated  to just  SSH. I  can cause  locking
errors with  HTTP too,  including some  interesting behavior  like files
unexpectedly being removed from the cloned repository.

For example,  after modifying a test  repo and then starting  a sync via
HTTP, I started a sync from another HTTP client which caused this:

$ f sync
Sync with http://amb@fossil:8080/
Round-trips: 24   Artifacts sent: 24  received: 0
Error: Database error: database is locked: {COMMIT}
Round-trips: 24   Artifacts sent: 24  received: 0
Sync finished with 3840799 bytes sent, 65248 bytes received

After  the second  sync  completed  (having received  a  partial set  of
artifacts),  I did  an update  and  suddenly files  began being  removed
(presumably due to the partial commit above).

After letting the original commit run  to completion another time, I did
an update in the second but the files have not come back:

On the first committer:
$ f stat | grep checkout
checkout:     4393b959511a32ec949f32900049d1195226f8d4 2014-04-19 01:05:46 UTC
$ ls | wc -l
     101

On the second:
$ f stat | grep checkout
checkout:     4393b959511a32ec949f32900049d1195226f8d4 2014-04-19 01:05:46 UTC
$ ls | wc -l
      31

Only after closing  and opening the local repository was  I able to make
the files come back,  but I wonder what would have  happened had I tried
to commit files during the time that it was in this state.

It's  possible that  using SSH  as  a client  makes it  easier to  cause
problems, but it does appear to be possible to run into issues with HTTP
as well. Once I even got told that a fork had happened (both clients had
autosync on). But it  seems to be due in part to  large commits and slow
disk.

I'll keep looking at it as I get time.

Andy
-- 
TAI64 timestamp: 400000005351d3f6


_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to