mirror of
https://github.com/007revad/Synology_enable_Deduplication.git
synced 2026-04-25 12:46:03 +03:00
[GH-ISSUE #78] Option visible but doesn't seem to work #195
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_Deduplication#195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rubenvarela on GitHub (Jul 20, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/78
Originally assigned to: @007revad on GitHub.
Trying to set this up, I see the option available when I go to,
I see both options, 'Automatic Deduplication' and 'Manual Deduplication'.
Manual Deduplication reads,
Automatic Deduplication reads 'Disabled on xxxx'
Under Manual Deduplication, when I select 'Run Now', it shows a quick 'Loading', it then returns, and nothing seems to happen. It still says "Status: Ready".
Happy to dig into it, but I'm trying to find ways of debugging. So far,
/var/log/systemd.logwhen I click 'Run Now', it adds an entry,systemd[1]: Started Synology Btrfs Deduplication Service./var/log/synobtrfsdedupe.logI see,if I
sudo ls /volume1/@dedupe/I do see content,No idea where to go from here.
@007revad commented on GitHub (Jul 22, 2024):
Which model Synology do you have?
What does the following command return?
@rubenvarela commented on GitHub (Jul 22, 2024):
Hey @007revad thanks for taking a look!
Output of the command,
@rubenvarela commented on GitHub (Jul 27, 2024):
@007revad I tried more stuff but couldn't find a way to fix the state.
What I ended up doing,
/volume1/@dedupeto@dedupe.backup@dedupeat this point wasn't createdIf I run the previous ls command, I now see more files under the folder,
Not sure if you'd like more info on setup or the actual backed up files. If not, I'm happy to close this at this point.
@007revad commented on GitHub (Jul 27, 2024):
Thanks for the feedback.
So the solution would be:
@dedupeI had assumed I'd be able to provide you the missing file(s) to put in
/volume1/@dedupebut after your previous reply I noticed I have a 1/volumeX@dedupe` folder for each volume that I've had dedupe enabled on. And the files in them are different sizes. Then I forgot to reply. Sorry.