tahoe-lafs/trac-2024-07-25

test whether it works to change encoding parameters for a new version of a mutable file #1390

New issue

Open

opened 2011-04-09 20:20:02 +00:00 by davidsarah · 1 comment

davidsarah commented

2011-04-09 20:20:02 +00:00

Owner

We don't appear to have unit tests for the case where different versions of a mutable file have different encoding parameters. The natural place for such tests to go would be source:src/allmydata/test/test_mutable.py (for no-network tests) and/or source:src/allmydata/test/test_system.py (for full system tests).

We don't appear to have unit tests for the case where different versions of a mutable file have different encoding parameters. The natural place for such tests to go would be source:src/allmydata/test/test_mutable.py (for no-network tests) and/or source:src/allmydata/test/test_system.py (for full system tests).

tahoe-lafs added the

labels 2011-04-09 20:20:02 +00:00

tahoe-lafs added this to the soon milestone 2011-04-09 20:20:02 +00:00

Brian Warner <warner@lothar.com> commented

2011-08-27 22:51:05 +00:00

Author

Owner

In changeset:370e6f271e40945b:

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.

In changeset:370e6f271e40945b: ``` 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. ```

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1390

No description provided.