[tahoe-dev] Change the parameters(K-N) when using

[Greg Troxel]

David-Sarah Hopwood <david-sarah at jacaranda.org> writes:

> Rebalancing, i.e. changing the parameters of existing files and putting
> shares in the optimal places, is less automatic than we would like it to be.
> Currently I think the easiest way to do that is to copy a directory tree
> from the grid to a local filesystem and then copy it back (to a new directory
> on the grid), then delete the original tree and allow its shares to expire.
>
> (Note that 'tahoe cp' directly from one grid directory to another will not
> have the desired effect, because the new tree will link to the old immutable
> files.)

So I wonder (as statements...):

  The fact that cp doesn't produce an output with encoding matching the
  current config is a bug.  It's ok to reuse conforming immutable files,
  but not to violate the expected postcondition.

  repair should have an option to consider an object unhealthy if the
  encoding either doesn't match, or is weaker than (or ?) the current
  config.  This is harder than regular repair because the URI will
  change so it really needs to be "when deep repairing a directory,
  objects in the directory might need recoding" - and then it gets
  scary.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110228/05c4e6f2/attachment.pgp>