mirror of
https://github.com/007revad/Synology_enable_Deduplication.git
synced 2026-04-25 12:46:03 +03:00
[GH-ISSUE #16] DSM 7.2 DS2422 64GB #181
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#181
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 @techguruz on GitHub (Jun 8, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/16
I am currently getting the following message when trying to run the script
ERROR Not enough memory installed for deduplication: 64 MB!
I have 64GB of ram, but it's not working for some reason.
@007revad commented on GitHub (Jun 9, 2023):
It sounds like dmidecode in DSM 7.2 on models with more than 8 drive bays reports memory in GB instead of MB.
What does the following command return?
sudo dmidecode -t memory | grep -i 'size'The Synology_enable_M2_volume also enables data deduplication, and doesn't check the amount of memory. As you've already the Synology_enable_M2_volume script you should have data deduplication available in storage manager.
@techguruz commented on GitHub (Jun 9, 2023):
when I run sudo dmidecode -t memory | grep -i 'size' I get
Size: 32 GB
Size: 32 GB
I don't have data deduplication available in the storage manager for some reason. Is this only available on NVMe drives or also SSD volumes?
@007revad commented on GitHub (Jun 9, 2023):
Excellent. I can change my script to check if it's GB or MB. I'll update the script so it works with MB or GB.
I've done data deduplication on a RAID 1 pair of NVMe drives on my DS1821+ with DSM 7.2 beta. I had to run Synology_HDD_db without the -f or --force option. If you use the -f or --force option you won't see the data deduplication option in storage manager.
Data deduplication requires the storage pool to be using Btrfs and only works on RAID 1 (and not on encrypted volumes). https://kb.synology.com/en-br/DSM/help/DSM/StorageManager/volume_btrfs_dedup?version=7
I just remembered that this script also enables or adds
support_btrfs_dedupe="yes"to synoinfo.conf and as you weren't able to run this script due to the false "not enough memory" errorsupport_btrfs_dedupe="yes"would be missing.Run this command:
sudo echo 'support_btrfs_dedupe="yes"' >> /etc.defaults/syninfo.confThen check the following command returns "yes":
sudo synogetkeyvalue /etc.defaults/syninfo.conf support_btrfs_dedupeYou should now have deduplication available in storage manager for any RAID 1 Btrfs storage pool consisting of SSD/NVMe drives.
@techguruz commented on GitHub (Jun 9, 2023):
When I Run this command:
sudo echo 'support_btrfs_dedupe="yes"' >> /etc.defaults/syninfo.conf
I get
-sh: /etc.defaults/syninfo.conf: Permission denied
I think synology have put things in place to stop users from editing the file in the 7.2 update.
I am using Btrfs ut not raid 1 so that explains why I am not seeing that option.
@007revad commented on GitHub (Jun 9, 2023):
Are you using the newest 7.2-64570 or the previous 7.2-64561 ?
@techguruz commented on GitHub (Jun 9, 2023):
7.2-64570
@007revad commented on GitHub (Jun 9, 2023):
Try the following commands:
sudo -isynosetkeyvalue /etc.defaults/synoinfo.conf support_btrfs_dedupe yessynogetkeyvalue /etc.defaults/synoinfo.conf support_btrfs_dedupe@007revad commented on GitHub (Jun 9, 2023):
Can you also try:
sudo -i synogetkeyvalue /etc.defaults/synoinfo.conf mem_max_mbsudo -i synogetkeyvalue /etc.defaults/synoinfo.conf mem_max_gb@techguruz commented on GitHub (Jun 9, 2023):
that one did the trick cheers buddy
@techguruz commented on GitHub (Jun 9, 2023):
so sudo -i synogetkeyvalue /etc.defaults/synoinfo.conf mem_max_mb
gives me 32768
but sudo -i synogetkeyvalue /etc.defaults/synoinfo.conf mem_max_gb
give me nothing at all
@techguruz commented on GitHub (Jun 9, 2023):
thinking about it could have something to do with the max officially supported memory being 32GB but I am running 64GB so could be throwing things off
@007revad commented on GitHub (Jun 9, 2023):
It looks like dmidecode in 7.2-64570 reports the installed memory size in GB (instead of MB like in previous DSM 7 versions including 7.2-64561). But the max memory in synoinfo.conf is still in MB.
This is 4th or 5th thing I've seen in DSM 7.2 that looks like Synology is trying to break my scripts.
@techguruz commented on GitHub (Jun 9, 2023):
To be fair it does seem like Synology change things just to make things difficult for people using scripts and unsupported hardware.
@007revad commented on GitHub (Jun 9, 2023):
I've released a new version that fixes GB/MB issue. https://github.com/007revad/Synology_enable_Deduplication/releases/tag/v1.0.9
@techguruz commented on GitHub (Jun 9, 2023):
cheers buddy working as intended
@007revad commented on GitHub (Jun 9, 2023):
Thanks for the feedback.