[tahoe-lafs-trac-stream] [tahoe-lafs] #1510: modifying SDMF file fails when tahoe.cfg's k/N differs from file

[tahoe-lafs]

#1510: modifying SDMF file fails when tahoe.cfg's k/N differs from file
------------------------------+-------------------------------------
     Reporter:  warner        |      Owner:  Brian Warner <warner@…>
         Type:  defect        |     Status:  closed
     Priority:  critical      |  Milestone:  1.9.0
    Component:  code-mutable  |    Version:  1.9.0a1
   Resolution:  fixed         |   Keywords:
Launchpad Bug:                |
------------------------------+-------------------------------------
Changes (by Brian Warner <warner@…>):

 * owner:   => Brian Warner <warner@…>
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [5216/trunk]:
 {{{
 #!CommitTicketReference repository="trunk" revision="5216"
 SDMF: update filenode with correct k/N after Retrieve. Fixes #1510.

 Without this, we get a regression when modifying a mutable file that was
 created with more shares (larger N) than our current tahoe.cfg . The
 modification attempt creates new versions of the (0,1,..,newN-1) shares,
 but
 leaves the old versions of the (newN,..,oldN-1) shares alone (and throws a
 assertion error in SDMFSlotWriteProxy.finish_publishing in the process).

 The mixed versions that result (some shares with e.g. N=10, some with
 N=20,
 such that both versions are recoverable) cause problems for the Publish
 code,
 even before MDMF landed. Might be related to refs #1390 and refs #1042.
 }}}

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