[volunteergrid2-l] Object Health

[Shawn Willden]

I think we decided a while ago to change that to 90 days.

On Mon, Jul 9, 2012 at 3:19 PM, Brad Rupp <bradrupp at gmail.com> wrote:

> The tahoe-dev folks are asking if servers on the grid were doing
> expiration.  I don't think so, but I thought I would ask to make sure.
>
> I assume all nodes on VG2 are still configured with 365 day leases. Does
> anyone have nodes that don't have this?
>
> Thanks,
>
> Brad
>
>
> On 7/5/2012 4:36 PM, Shawn Willden wrote:
>
>> I think this is a question for tahoe-dev.
>>
>> On Thu, Jul 5, 2012 at 4:15 PM, Brad Rupp <bradrupp at gmail.com
>> <mailto:bradrupp at gmail.com>> wrote:
>>
>>     Greetings VG2 friends,
>>
>>     I have a question about object health in Tahoe.  If I run two
>>     repairs, one right after another, the second repair quite often has
>>     unhealthy objects.  I have not backed up any files to the grid
>>     between these two repairs.  I would expect the second repair to not
>>     have any unhealthy objects.
>>
>>     I am running the following command:
>>
>>     ~/tahoe/bin/tahoe deep-check --repair --verbose my-alias:
>>
>>     The output from repair #1:
>>
>>     repair successful
>>     done: 11801 objects checked
>>       pre-repair: 11725 healthy, 76 unhealthy
>>       76 repairs attempted, 76 successful, 0 failed
>>       post-repair: 11801 healthy, 0 unhealthy
>>
>>     The output from repair #2:
>>     done: 11801 objects checked
>>       pre-repair: 11789 healthy, 12 unhealthy
>>       12 repairs attempted, 11 successful, 1 failed
>>       post-repair: 11800 healthy, 1 unhealthy
>>
>>     As you can see, the first repair found and fixed 76 unhealthy
>>     objects. The second repair, approximately 12 hours later, found 12
>>     unhealthy objects and fixed 11 of them.
>>
>>     Why would the second repair find 12 unhealthy objects?  I would have
>>     expected it to find 0 unhealthy objects given that the first repair
>>     was performed only 12 hours earlier.
>>
>>     This is just one repair run out of many.  I can consistently get
>>     similar results.  I guess the deeper question is are the objects
>>     stored in Tahoe safe?  Or when I really need them due to a
>>     catastrophic event will I lose a handful of objects due to this?
>>
>>     Regards,
>>
>>     Brad
>>     ______________________________**___________________
>>     volunteergrid2-l mailing list
>>     volunteergrid2-l at tahoe-lafs.__**org
>>     <mailto:volunteergrid2-l@**tahoe-lafs.org<volunteergrid2-l at tahoe-lafs.org>
>> >
>>     https://tahoe-lafs.org/cgi-__**bin/mailman/listinfo/__**
>> volunteergrid2-l<https://tahoe-lafs.org/cgi-__bin/mailman/listinfo/__volunteergrid2-l>
>>     <https://tahoe-lafs.org/cgi-**bin/mailman/listinfo/**volunteergrid2-l<https://tahoe-lafs.org/cgi-bin/mailman/listinfo/volunteergrid2-l>
>> >
>>     http://bigpig.org/twiki/bin/__**view/Main/WebHome<http://bigpig.org/twiki/bin/__view/Main/WebHome>
>>     <http://bigpig.org/twiki/bin/**view/Main/WebHome<http://bigpig.org/twiki/bin/view/Main/WebHome>
>> >
>>
>>
>>
>>
>> --
>> Shawn
>>
>>
>>
>> ______________________________**_________________
>> volunteergrid2-l mailing list
>> volunteergrid2-l at tahoe-lafs.**org <volunteergrid2-l at tahoe-lafs.org>
>> https://tahoe-lafs.org/cgi-**bin/mailman/listinfo/**volunteergrid2-l<https://tahoe-lafs.org/cgi-bin/mailman/listinfo/volunteergrid2-l>
>> http://bigpig.org/twiki/bin/**view/Main/WebHome<http://bigpig.org/twiki/bin/view/Main/WebHome>
>>
>>
> ______________________________**_________________
> volunteergrid2-l mailing list
> volunteergrid2-l at tahoe-lafs.**org <volunteergrid2-l at tahoe-lafs.org>
> https://tahoe-lafs.org/cgi-**bin/mailman/listinfo/**volunteergrid2-l<https://tahoe-lafs.org/cgi-bin/mailman/listinfo/volunteergrid2-l>
> http://bigpig.org/twiki/bin/**view/Main/WebHome<http://bigpig.org/twiki/bin/view/Main/WebHome>
>



-- 
Shawn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tahoe-lafs.org/cgi-bin/mailman/private/volunteergrid2-l/attachments/20120709/d921af4b/attachment.html>