[tahoe-lafs-trac-stream] [tahoe-lafs] #818: Output of tahoe deep-check --repair is hard to skim

tahoe-lafs trac at tahoe-lafs.org
Sun Sep 1 16:43:56 UTC 2013


#818: Output of tahoe deep-check --repair is hard to skim
----------------------------+----------------------------------------------
     Reporter:  kpreid      |      Owner:
         Type:              |     Status:  new
  enhancement               |  Milestone:  1.12.0
     Priority:  minor       |    Version:  1.4.1
    Component:  code-       |   Keywords:  deep-check easy repair usability
  frontend-cli              |
   Resolution:              |
Launchpad Bug:              |
----------------------------+----------------------------------------------
Changes (by daira):

 * milestone:  undecided => 1.12.0


Old description:

> The summary output of tahoe deep-check looks exactly the same, except for
> the numbers, no matter whether everything is fine or files needed to be
> repaired. For easier scanning, especially in a log of multiple deep-check
> operations at different times or of different files, it should have fewer
> statements that there were 0 of something; for example, in the simple
> case of all files being healthy, a statement like “5 files checked and
> found healthy.” would be good, as opposed to the current:
>
> {{{
> done: 5 objects checked
>  pre-repair: 5 healthy, 0 unhealthy
>  0 repairs attempted, 0 successful, 0 failed
>  post-repair: 5 healthy, 0 unhealthy
> }}}
>
> Also, the output does not include any feedback that --add-lease did its
> thing, but that is perhaps a separate issue.

New description:

 The summary output of tahoe deep-check looks exactly the same, except for
 the numbers, no matter whether everything is fine or files needed to be
 repaired. For easier scanning, especially in a log of multiple deep-check
 operations at different times or of different files, it should have fewer
 statements that there were 0 of something; for example, in the simple case
 of all files being healthy, a statement like “5 files checked and found
 healthy.” would be good, as opposed to the current:

 {{{
 done: 5 objects checked
  pre-repair: 5 healthy, 0 unhealthy
  0 repairs attempted, 0 successful, 0 failed
  post-repair: 5 healthy, 0 unhealthy
 }}}

 Also, the output does not include any feedback that --add-lease did its
 thing, but that is perhaps a separate issue.

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/818#comment:4>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list