[GH-ISSUE #73] Support for qemu ssd disk? #13

Open
opened 2026-03-07 19:09:59 +03:00 by kerem · 6 comments
Owner

Originally created by @dur3x on GitHub (May 30, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/73

Originally assigned to: @007revad on GitHub.

Hello :-)
I'm curious to testing this thing and I tried it on Xpenology - DS3622xs+ - setup on top of proxmox with emulated QEMU (ssd) disks.

Information are:

root@ds3622xs-2:# synogetkeyvalue /etc/synoinfo.conf support_btrfs_dedupe
yes
root@ds3622xs-2:# synogetkeyvalue /etc.defaults/synoinfo.conf support_btrfs_dedupe
yes

root@ds3622xs-2:~# ./syno_enable_dedupe.sh --check
Synology_enable_Deduplication v1.3.25
DS3622xs+ DSM 7.2.1-69057-5

StorageManager 1.0.0-0017

Using options: --check
Running from: /root/syno_enable_dedupe.sh

NAS has 4 GB of memory.

Btrfs Data Deduplication is enabled.

Tiny Btrfs Data Deduplication is enabled.

Checking non-Synology drive supported.
File is already edited.

Checking value in backup file.
Backup file is okay.

Screenshot 2024-05-30 at 23 18 23 Screenshot 2024-05-30 at 23 18 08

Thanks in advance for your help

Originally created by @dur3x on GitHub (May 30, 2024). Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/73 Originally assigned to: @007revad on GitHub. Hello :-) I'm curious to testing this thing and I tried it on Xpenology - DS3622xs+ - setup on top of proxmox with emulated QEMU (ssd) disks. Information are: root@ds3622xs-2:# synogetkeyvalue /etc/synoinfo.conf support_btrfs_dedupe yes root@ds3622xs-2:# synogetkeyvalue /etc.defaults/synoinfo.conf support_btrfs_dedupe yes root@ds3622xs-2:~# ./syno_enable_dedupe.sh --check Synology_enable_Deduplication v1.3.25 DS3622xs+ DSM 7.2.1-69057-5 StorageManager 1.0.0-0017 Using options: --check Running from: /root/syno_enable_dedupe.sh NAS has 4 GB of memory. Btrfs Data Deduplication is enabled. Tiny Btrfs Data Deduplication is enabled. Checking non-Synology drive supported. File is already edited. Checking value in backup file. Backup file is okay. <img width="1280" alt="Screenshot 2024-05-30 at 23 18 23" src="https://github.com/007revad/Synology_enable_Deduplication/assets/5813331/d7699464-67ed-49e8-a941-38d339ef26f5"> <img width="729" alt="Screenshot 2024-05-30 at 23 18 08" src="https://github.com/007revad/Synology_enable_Deduplication/assets/5813331/555b105c-d94a-468c-80cf-e5db66a40650"> Thanks in advance for your help
Author
Owner

@007revad commented on GitHub (May 30, 2024):

It can take up to 20 minutes before the dedupe menu option appears. If storage manager was already open you also need to close and reopen it.

<!-- gh-comment-id:2140888155 --> @007revad commented on GitHub (May 30, 2024): It can take up to 20 minutes before the dedupe menu option appears. If storage manager was already open you also need to close and reopen it.
Author
Owner

@dur3x commented on GitHub (May 30, 2024):

It can take up to 20 minutes before the dedupe menu option appears. If storage manager was already open you also need to close and reopen it.

Thanks for your quick answer :-) I will have a look tomorrow and keep you in touch

<!-- gh-comment-id:2140893225 --> @dur3x commented on GitHub (May 30, 2024): > It can take up to 20 minutes before the dedupe menu option appears. If storage manager was already open you also need to close and reopen it. Thanks for your quick answer :-) I will have a look tomorrow and keep you in touch
Author
Owner

@dur3x commented on GitHub (Jun 1, 2024):

I probably miss something because the menu is still not appear :'(
Do you have some hints/things to check ?

<!-- gh-comment-id:2143345115 --> @dur3x commented on GitHub (Jun 1, 2024): I probably miss something because the menu is still not appear :'( Do you have some hints/things to check ?
Author
Owner

@007revad commented on GitHub (Jun 2, 2024):

NAS has 4 GB of memory.

Btrfs Data Deduplication is enabled.

Tiny Btrfs Data Deduplication is enabled.

I'm wondering how "Btrfs Data Deduplication" got enabled when the DS3622xs+ does not have it enabled in DSM 7.2.1, and the script thinks it only has 4GB of memory.

  • Btrfs Tiny Data Deduplication requires 4GB of memory or more.
  • Btrfs Data Deduplication requires 16GB of memory or more.

Do you have usage details enabled? https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/volume_view_usage?version=7

Storage Manager checks if drives are SSD or not. What does this command return?

syno_hdd_util --ssd_detect
<!-- gh-comment-id:2144001579 --> @007revad commented on GitHub (Jun 2, 2024): > NAS has 4 GB of memory. > > Btrfs Data Deduplication is enabled. > > Tiny Btrfs Data Deduplication is enabled. I'm wondering how "Btrfs Data Deduplication" got enabled when the DS3622xs+ does not have it enabled in DSM 7.2.1, and the script thinks it only has 4GB of memory. - Btrfs Tiny Data Deduplication requires 4GB of memory or more. - Btrfs Data Deduplication requires 16GB of memory or more. Do you have usage details enabled? https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/volume_view_usage?version=7 Storage Manager checks if drives are SSD or not. What does this command return? ``` syno_hdd_util --ssd_detect ```
Author
Owner

@dur3x commented on GitHub (Jun 2, 2024):

To be honest there are both btrfs and tiny btfrs because I set manually, for testing, the btfrs value. I can easily reset it.
I also tested on two others instances SA6300 and DS720+ and I have the same problem. All of these xpenology setups are done with the same virtual disks from proxmox so I suppose it's linked to my virtual disks.

The command you gave returns this:

root@ds3622xs-2:~# syno_hdd_util --ssd_detect
Model                Firmware     SN                   Dev        is SSD?
HARDDISK             2.5+         QM00009              /dev/sdc   yes
HARDDISK             2.5+         QM00007              /dev/sdb   yes
<!-- gh-comment-id:2144004929 --> @dur3x commented on GitHub (Jun 2, 2024): To be honest there are both btrfs and tiny btfrs because I set manually, for testing, the btfrs value. I can easily reset it. I also tested on two others instances SA6300 and DS720+ and I have the same problem. All of these xpenology setups are done with the same virtual disks from proxmox so I suppose it's linked to my virtual disks. The command you gave returns this: ``` root@ds3622xs-2:~# syno_hdd_util --ssd_detect Model Firmware SN Dev is SSD? HARDDISK 2.5+ QM00009 /dev/sdc yes HARDDISK 2.5+ QM00007 /dev/sdb yes ```
Author
Owner

@007revad commented on GitHub (Jun 2, 2024):

It is looking like it's a an issue with virtual disks. Xpenology, proxmox and virtual disks are all beyond my level of knowledge.

<!-- gh-comment-id:2144008791 --> @007revad commented on GitHub (Jun 2, 2024): It is looking like it's a an issue with virtual disks. Xpenology, proxmox and virtual disks are all beyond my level of knowledge.
Sign in to join this conversation.
No labels
pull-request
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
starred/Synology_enable_Deduplication#13
No description provided.