Tv of Sv carefully and repeatdly confirmed, at my request, that after he gets this exception that the new child does exist in the directory! So this exception is somehow not preventing the directory from being updated!
He wrote:
Yeah, I confirmed it again just now. I took a file already
backed up, 100k11, reversed it with tac, saved it a different
dir in TestFiles1M as 100k12, did tahoe backup, and got the
error message. I did tahoe ls -l and can see 100k12 in the
correct location, and can successfully see its contents with
tahoe get.
Here's tahoe ls -l after and before:
[root@ls-126 ~]# tahoe ls -l Ss1/Archives/2013-05-07_21:26:17Z
-r-- 104726 May 01 10:26 100k1
-r-- 104433 May 07 14:23 100k12
-r-- 103983 May 01 10:26 100k2
-r-- 104187 May 01 10:26 100k3
-r-- 104850 May 01 10:26 100k4
-r-- 104699 May 03 11:42 100k5
dr-x - May 01 10:26 d1
dr-x - May 01 10:26 d2
dr-x - May 01 10:27 d3
[root@ls-126 ~]# tahoe ls -l Ss1/Archives/2013-05-07_00:28:11Z
-r-- 104726 May 01 10:26 100k1
-r-- 103983 May 01 10:26 100k2
-r-- 104187 May 01 10:26 100k3
-r-- 104850 May 01 10:26 100k4
-r-- 104699 May 03 11:42 100k5
dr-x - May 01 10:26 d1
dr-x - May 01 10:26 d2
dr-x - May 01 10:27 d3
