Dedup did not work fully when uploaded same file 4 times

[jeniawhite]

Environment info

• Version: output of git rev-parse HEAD | package.json | UI
• Deployment: N/A | Dev | VBox | ESX | GCloud | AWS
• Customer: N/A | QA | name

Actual behaviour

1. • Created a new bucket with policy of 1 pool with 3 nodes (all okay)
   • Uploaded 3mb file (not video/no special replicas) that created 6 parts
   • Waited that everything replicated correctly and that the blocks/chunks/parts are accessible
   • Uploaded same file ones again with a different name
   • Waited that everything replicated correctly and that the blocks/chunks/parts are accessible
   • Saw in DB that there was a full dedup (everything correct till now)
   • Uploaded same file ones again with a different name
   • Waited that everything replicated correctly and that the blocks/chunks/parts are accessible
   • Saw in DB that we created 6 more chunks which means that we did not dedup 0%
   • Afterwards did same thing with the 4th file and got a 100% dedup

Expected behavior

1. I should see 100% all of the time and only have 6 chunks (like parts count of the first file)

Steps to reproduce

1. Explained above

Screenshots or Logs or other output that would be helpful

(If large, please upload as attachment)

[guymguym]

@nimrod-becker This is too old and stale by now. We should either reproduce on master or close.

[nimrod-becker]

Reproduced by Liran

[guymguym]

I will add a unit test that writes same file repeatedly and verifies that it always finds dedup.

[nimrod-becker]

Per guy's comment, closing this one

[guymguym]

Keeping open as a reminder to commit the test

[github-actions[bot]]

This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed.