After some investigations rebalance seems to work. Here is the test :
stop the 2nd node. Upload a file on node 1. Starting node 2 and do a "check --repair" => nothing. Now, in node1, rm .tahoe/storage/shares/de/derbnumtsxwu7rhydpxtxizd5y/1 and do a check --repair, the file is created on node2. I supposed the files named 0 and 1 corresponding to the index of node (in my case 0 => node1 and 1=>node2) May i right or wrong ? I've only got 4 files, so it was "easy", but how to achieve this with tons of files ? 2013/2/14 Paul Rabahy <[email protected]> > It looks like https://tahoe-lafs.org/trac/tahoe-lafs/ticket/699 is > related. > > > On Thu, Feb 14, 2013 at 10:01 AM, Greg Troxel <[email protected]> wrote: > >> >> thierry dijoux <[email protected]> writes: >> >> > Thanks Paul for the reply. >> > Just did the test, and a "tahoe check --repair" doesn't rebalance the >> file. >> > I also try a deep-check --repair, no more success. >> >> I suspect it would be good to have two notions of "healthy", one based >> on enough shares, and one based on meeting the distribution criteria. I >> see the "should be 1 and 1 but is 2 and 0" situation as scarier than >> "should be 10 on 10 servers, but is 9 on 9 servers". >> >> _______________________________________________ >> tahoe-dev mailing list >> [email protected] >> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev >> >> > > _______________________________________________ > tahoe-dev mailing list > [email protected] > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev > >
_______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
