3 subject="""comment 2"""
4 date="2020-10-22T17:00:25Z"
6 Implemented that. But..
8 As implemented, there's nothing to make the chunk size get stored in the
9 chunk log for a key, after it accesses its content using the configured
12 So, changing the chunk= of the remote can prevent accessing content that
13 was accessible before. Of course, avoiding that is why chunk sizes are
14 logged in the first place.
16 Seems like maybe fsck --from should fix the chunk log? I think
17 fsck would always need to be used, to fix up the location log, before any
18 other commands rely on the data being in the special remote, so it seems
19 fine to only fix the chunk log there.
21 But, also a bit unclear how fsck would find out when it needs to do this.
22 It only needs to when the remote's configured chunk size is not
23 listed in the chunk log. But that's also common after changing the chunk
24 size of a remote. So it would have to mess around with checking the
25 presence of chunk keys itself, which would be extra work and also ugly
28 I'm leaving this todo^Wbug open for now due to this.