[volunteergrid2-l] Very soon after uploading, checks failing.

[Brad Rupp]

I posted something about this several months ago.  I always see similar 
results.  As I said back then, Tahoe is a cool concept but it is not 
ready for prime time.

Brad

On 11/23/2012 5:52 AM, Ruben Pollan wrote:
> Quoting Aaron Drew (2012-11-23 12:06:27)
>> I have spent about 2 weeks uploading 60GB of my most important data to tahoe
>> (using duplicity for backups) and as soon as I'm finished, I do a check and get
>> this output:
>>
>> $ tahoe deep-check riot-backup:
>> 100 objects checked..
>> 200 objects checked..
>> 300 objects checked..
>> 400 objects checked..
>> 500 objects checked..
>> 600 objects checked..
>> 700 objects checked..
>> 800 objects checked..
>> 900 objects checked..
>> 1000 objects checked..
>> 1100 objects checked..
>> 1200 objects checked..
>> 1300 objects checked..
>> 1400 objects checked..
>> 1500 objects checked..
>> 1600 objects checked..
>> 1700 objects checked..
>> 1800 objects checked..
>> 1900 objects checked..
>> 2000 objects checked..
>> 2100 objects checked..
>> done: 2147 objects checked, 592 healthy, 1555 unhealthy
>
> I just check the backup I did a couple of weeks ago and I get more or less the
> same result :(
>
> $ tahoe deep-check backup
> 100 objects checked..
> 200 objects checked..
> 300 objects checked..
> 400 objects checked..
> 500 objects checked..
> done: 558 objects checked, 44 healthy, 514 unhealthy
>
>
>> Seriously? All nodes are available. How is this possible? Have people been
>> swapping out disks (1/3rd of them!?)?
>
> Yesterday there was a power cut that affected the hard disk that I use for
> tahoe, but not the server. So the computer was up but not the disk. That happend
> from 17:00 GMT to 23:00 GMT, but now it is up again.
>
>