[tahoe-lafs-trac-stream] [tahoe-lafs] #1395: error doing a check --verify on files bigger than about 1Gbyte

[tahoe-lafs]

#1395: error doing a check --verify on files bigger than about 1Gbyte
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  zooko
  sickness               |     Status:  assigned
         Type:  defect   |  Milestone:  1.9.0
     Priority:  major    |    Version:  1.8.2
    Component:  code-    |   Keywords:  memory verify error performance
  encoding               |  review-needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 davidsarah: hmm, if the storage server got clobbered by all the parallel
 fetches, then it would throw {{{MemoryError}}} (and either crash
 completely, or at least return Failures to the {{{remote_read()}}} calls).
 From the client's point of view, this is identical to there being no
 shares available: crashing servers are not providing shares.

 Maybe the CLI command output could be extended to mention how many servers
 were contacted, and how many answered, so the user could distinguish
 crashing-servers (or no-network) from solid NAKs.

 This patch is still important to apply, though.. zooko: please don't defer
 reviewing it because of the CLI deficiency. It'll be easier to test a CLI
 change with special-purpose test code (building a client with no servers,
 or with intentionally-failing servers) than by trying to provoke a
 {{{MemoryError}}}.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1395#comment:26>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage