<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<STYLE type=text/css> <!--@import url(scrollbar.css); --></STYLE>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE> body{FONT-SIZE:12pt; FONT-FAMILY:宋体,serif;} </STYLE>
<META name=GENERATOR content="MSHTML 9.00.8112.16502"><BASE
target=_blank></HEAD>
<BODY
style="LINE-HEIGHT: 1.3; BORDER-RIGHT-WIDTH: 0px; MARGIN: 12px; BORDER-TOP-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px"
marginheight="0" marginwidth="0">
<DIV><FONT color=#000000 size=3 face=宋体><FONT
face=Verdana>I</FONT> <FONT face=Verdana>have done something about this. I
have written some code for tahoe to automatically schedule repair process. the
basic idea like this: run a monitor service when tahoe client runs, detect
file's health'state when downloading a file, if the file is unhealthy(the valid
shares < a threshold number), then record this file, and at a scheduled
time(maybe at midnight), run a repair service to make this
file healthy...</FONT></FONT></DIV>
<DIV><FONT size=3 face=Verdana>My problem is how to make a test to this? I think
this way can save much resources consumed by a repair process. I
know there are simulators in the source code folder of tahoe, but I donnot know
how to use it to test this repair process. I want to
know whether this way to repair files can provide a good way to
save repair overhead compared with original way and keep a high
availability at the same time.</FONT></DIV>
<DIV> </DIV>
<DIV align=left><FONT color=#c0c0c0 size=2 face=Verdana>2013-08-15</FONT></DIV>
<DIV align=left><FONT size=2 face=Verdana>
<HR style="WIDTH: 122px; HEIGHT: 2px" id=SignNameHR align=left SIZE=2>
</FONT></DIV>
<DIV align=left><FONT color=#c0c0c0 size=2 face=Verdana><SPAN id=_FlashSignName>
<STYLE type=text/css>
body {
font-size:12.1pt; font-family:simsun,serif;
}
</STYLE>
<!-- flashmail style begin -->
<STYLE type=text/css> <!--@import url(C:\Program Files\Netease\网易闪电邮\\data\scrollbar.css); -->
blockquote {
margin-top:0; margin-bottom:0; margin-left:2em;
}
body {
padding:0; margin:0;
}
</STYLE>
<BASE target=_blank><!-- flashmail style end -->
<META name=GENERATOR content="MSHTML 9.00.8112.16443">
<DIV><FONT face=Verdana>Regards,</FONT></DIV>
<DIV><FONT face=Verdana>han zheng</FONT></DIV></STATIONERY></SPAN></FONT></DIV>
<DIV><FONT size=2 face=Verdana>
<HR>
</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>发件人：</STRONG>"tahoe-lafs"
<trac@tahoe-lafs.org></FONT></DIV>
<DIV><FONT size=2
face=Verdana><STRONG>发送时间：</STRONG>2013-07-04 00:49</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>主题：</STRONG>Re: [tahoe-lafs] #643:
Automatically schedule repair process (and backups?)</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>收件人：</STRONG></FONT></DIV>
<DIV><FONT size=2
face=Verdana><STRONG>抄送：</STRONG>"tahoe-lafs-trac-stream"<tahoe-lafs-trac-stream@tahoe-lafs.org></FONT></DIV>
<DIV><FONT size=2 face=Verdana></FONT> </DIV>
<DIV><FONT size=2 face=Verdana>
<DIV>#643: Automatically schedule repair process (and backups?) </DIV>
<DIV>-------------------------+------------------------------------------------- </DIV>
<DIV> Reporter: mmore | Owner: somebody </DIV>
<DIV> Type: | Status: new </DIV>
<DIV> enhancement | Milestone: eventually </DIV>
<DIV> Priority: major | Version: 1.3.0 </DIV>
<DIV> Component: | Keywords: repair availability preservation </DIV>
<DIV> operational | usability scheduling tahoe-backup </DIV>
<DIV> Resolution: | </DIV>
<DIV>Launchpad Bug: | </DIV>
<DIV>-------------------------+------------------------------------------------- </DIV>
<DIV> </DIV>
<DIV>Old description: </DIV>
<DIV> </DIV>
<DIV>> 1.have Tahoe an automatic repair, i.e. , the introducer monitor the </DIV>
<DIV>> replicas numbers, for example if we have configuration of 10 /3 , so </DIV>
<DIV>> introducer trigger repair process when the replicas became only 4 to keep </DIV>
<DIV>> the file available? </DIV>
<DIV>> 2. what are the threshold that triggers the repair process? </DIV>
<DIV> </DIV>
<DIV>New description: </DIV>
<DIV> </DIV>
<DIV> 1.have Tahoe an automatic repair, i.e. , the introducer monitor the </DIV>
<DIV> replicas numbers, for example if we have configuration of 10 /3 , so </DIV>
<DIV> introducer trigger repair process when the replicas became only 4 to keep </DIV>
<DIV> the file available? </DIV>
<DIV> 2. what are the threshold that triggers the repair process? </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV> </DIV>
<DIV>Comment (by zhan0903): </DIV>
<DIV> </DIV>
<DIV> Is there some implementation about automatical repair? I found it is not </DIV>
<DIV> convenient to repair only one file or directory every time you run the </DIV>
<DIV> repair tool </DIV>
<DIV> </DIV>
<DIV> sometimes, you even donnot know which file should be repaired, so I think </DIV>
<DIV> it will be good to make this tool run as a service and check files </DIV>
<DIV> automatically based on some principles or algorithm </DIV>
<DIV> </DIV>
<DIV> actually, I would like to do something about that </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/643#comment:17> </DIV>
<DIV>tahoe-lafs <https://tahoe-lafs.org> </DIV>
<DIV>secure decentralized storage </DIV></FONT></DIV></BODY></HTML>