[volunteergrid2-l] tahoe backup re-uploads old files

[Shawn Willden]

I have seen plenty of cases where a re-upload causes some shares to be
re-placed because of changes in the available node set, but I haven't seen
a case where Tahoe decided no shares were available.

I'd ask the dev list.

On Fri, Feb 24, 2012 at 12:12 AM, Marco Tedaldi <marco.tedaldi at gmail.com>wrote:

> Hello everyone
>
> Today it was finally done. The first full backup of my digital pictures
> was finished.
> Now, I immedediately started a new run to get the changes since the
> start of the last run into the backup as well.
>
> To my surprise it skipped some old pictures (which I consider normal)
> but started uploading one of the old pictures I had for sure not touched
> in the mean time.
>
> I've seen this behavior in the past as well when I restarted the backup
> after it had failed to complete. So I just blamed it on the old,
> incomplete run. But now, I don't really have an Idea why tahoe should
> upload this file again.
>
> It also states on the web interface, that there are no shares already
> present. Which is quite surprising as the whole file should already be
> there!
>
> I'm using tahoe 1.8.3.
> Any Ideas or should I go and ask on the dev-list?
>
> best regards
>
> Marco
> _______________________________________________
> volunteergrid2-l mailing list
> volunteergrid2-l at tahoe-lafs.org
> http://tahoe-lafs.org/cgi-bin/mailman/listinfo/volunteergrid2-l
> http://bigpig.org/twiki/bin/view/Main/WebHome
>



-- 
Shawn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/cgi-bin/mailman/private/volunteergrid2-l/attachments/20120224/49c5b07e/attachment.html>