starred/Synology_enable_Deduplication
1
0
Fork 0
mirror of https://github.com/007revad/Synology_enable_Deduplication.git synced 2026-04-25 12:46:03 +03:00
Code Issues 28 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #45] Script reports to be run from M.2 when using M2. SSD cache on volume #188

New issue
Closed
opened 2026-03-11 03:01:46 +03:00 by kerem · 13 comments
kerem commented 2026-03-11 03:01:46 +03:00
Owner
Copy link

Originally created by @herbingk on GitHub (Jan 5, 2024).
Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/45

Originally assigned to: @007revad on GitHub.

Script reports to be run from M,2 when using M2. SSD cache on volume. Same occurs for Synology_HDD_DB script as well.

cat /proc/mdstat command returns the following on my DS1621+

Personalities : [raid1] [raid6] [raid5] [raid4] [raidF1]
md3 : active raid1 nvme1n1p1[1] nvme0n1p1[0]
1000196800 blocks super 1.2 [2/2] [UU]

md2 : active raid5 sata1p3[0] sata3p3[2] sata4p3[3] sata5p3[4] sata6p3[5] sata2p3[1]
37453707840 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]

md1 : active raid1 sata1p2[0] sata4p2[5] sata5p2[4] sata6p2[3] sata3p2[2] sata2p2[1]
2097088 blocks [6/6] [UUUUUU]

md0 : active raid1 sata1p1[0] sata4p1[5] sata5p1[4] sata6p1[3] sata3p1[2] sata2p1[1]
8388544 blocks [6/6] [UUUUUU]

unused devices:

Thanks for looking into it.

Originally created by @herbingk on GitHub (Jan 5, 2024). Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/45 Originally assigned to: @007revad on GitHub. Script reports to be run from M,2 when using M2. SSD cache on volume. Same occurs for Synology_HDD_DB script as well. cat /proc/mdstat command returns the following on my DS1621+ Personalities : [raid1] [raid6] [raid5] [raid4] [raidF1] md3 : active raid1 nvme1n1p1[1] nvme0n1p1[0] 1000196800 blocks super 1.2 [2/2] [UU] md2 : active raid5 sata1p3[0] sata3p3[2] sata4p3[3] sata5p3[4] sata6p3[5] sata2p3[1] 37453707840 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU] md1 : active raid1 sata1p2[0] sata4p2[5] sata5p2[4] sata6p2[3] sata3p2[2] sata2p2[1] 2097088 blocks [6/6] [UUUUUU] md0 : active raid1 sata1p1[0] sata4p1[5] sata5p1[4] sata6p1[3] sata3p1[2] sata2p1[1] 8388544 blocks [6/6] [UUUUUU] unused devices: <none> Thanks for looking into it.
kerem closed this issue 2026-03-11 03:01:51 +03:00
kerem commented 2026-03-11 03:01:57 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jan 5, 2024):

Looks like I'll have to setup an NVMe read cache for 1 of my volumes to see what the script is doing wrong.

<!-- gh-comment-id:1879277915 --> @007revad commented on GitHub (Jan 5, 2024): Looks like I'll have to setup an NVMe read cache for 1 of my volumes to see what the script is doing wrong.
kerem commented 2026-03-11 03:02:02 +03:00
Author
Owner
Copy link

@herbingk commented on GitHub (Jan 6, 2024):

Just did a quick check and confirm, by disabling the M.2 SSD cache, the warning disappears.

<!-- gh-comment-id:1879751521 --> @herbingk commented on GitHub (Jan 6, 2024): Just did a quick check and confirm, by disabling the M.2 SSD cache, the warning disappears.
kerem commented 2026-03-11 03:02:07 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jan 6, 2024):

Ok. I've done some testing and I get the warning if the scriptpath variable is empty or contains a volume# that does not exist.

If you try this test script what does it return?
https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh

<!-- gh-comment-id:1879824489 --> @007revad commented on GitHub (Jan 6, 2024): Ok. I've done some testing and I get the warning if the scriptpath variable is empty or contains a volume# that does not exist. If you try this test script what does it return? https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh
kerem commented 2026-03-11 03:02:12 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jan 6, 2024):

When you run syno_enable_dedupe.sh what does the 4th or 5th line show?

It should show the path and filename of the script, like: Running from: /volume1/scripts/syno_enable_dedupe.sh

<!-- gh-comment-id:1879827068 --> @007revad commented on GitHub (Jan 6, 2024): When you run syno_enable_dedupe.sh what does the 4th or 5th line show? It should show the path and filename of the script, like: `Running from: /volume1/scripts/syno_enable_dedupe.sh`
kerem commented 2026-03-11 03:02:18 +03:00
Author
Owner
Copy link

@herbingk commented on GitHub (Jan 6, 2024):

When you run syno_enable_dedupe.sh what does the 4th or 5th line show?

It should show the path and filename of the script, like: Running from: /volume1/scripts/syno_enable_dedupe.sh

Running from: /volume1/admin/Synology_enable_Deduplication/syno_enable_dedupe.sh

<!-- gh-comment-id:1879834042 --> @herbingk commented on GitHub (Jan 6, 2024): > When you run syno_enable_dedupe.sh what does the 4th or 5th line show? > > It should show the path and filename of the script, like: `Running from: /volume1/scripts/syno_enable_dedupe.sh` Running from: /volume1/admin/Synology_enable_Deduplication/syno_enable_dedupe.sh
kerem commented 2026-03-11 03:02:23 +03:00
Author
Owner
Copy link

@herbingk commented on GitHub (Jan 6, 2024):

Ok. I've done some testing and I get the warning if the scriptpath variable is empty or contains a volume# that does not exist.

If you try this test script what does it return? https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh

/volume1/scripts/test.sh
scriptvol: volume1
vg: vg1
md: md3
md2
WARNING Don't store this script on an NVMe volume!

<!-- gh-comment-id:1879834603 --> @herbingk commented on GitHub (Jan 6, 2024): > Ok. I've done some testing and I get the warning if the scriptpath variable is empty or contains a volume# that does not exist. > > If you try this test script what does it return? https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh /volume1/scripts/test.sh scriptvol: volume1 vg: vg1 md: md3 md2 WARNING Don't store this script on an NVMe volume!
kerem commented 2026-03-11 03:02:28 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jan 6, 2024):

Strange. It doesn't do that for me.

I currently have 4 volumes:

  1. volume1 is on HDDs
  2. volume3 is on an NVMe drive in the DS1821+
  3. volume4 is on a pair of NVMe drives in a E10M20-T1
  4. volume5 is on a HDD

And a SATA SSD as a read cache for volume 5.

/volume1/scripts/test.sh
scriptvol: volume1
vg: vg1
md: md3
md2

/volume3/scripts/test.sh
scriptvol: volume3
vg: vg3
md: md4
WARNING Don't store this script on an NVMe volume!

/volume4/scripts/test.sh
scriptvol: volume4
vg: vg4
md: md5
WARNING Don't store this script on an NVMe volume!

/volume5/scripts/test.sh
scriptvol: volume5
vg: vg5
md: md6

I just noticed that you and I are somehow getting an extra md2 on the line after "md: md3" for volume1.

<!-- gh-comment-id:1879842488 --> @007revad commented on GitHub (Jan 6, 2024): Strange. It doesn't do that for me. I currently have 4 volumes: 1. volume1 is on HDDs 2. volume3 is on an NVMe drive in the DS1821+ 3. volume4 is on a pair of NVMe drives in a E10M20-T1 4. volume5 is on a HDD And a SATA SSD as a read cache for volume 5. ``` /volume1/scripts/test.sh scriptvol: volume1 vg: vg1 md: md3 md2 /volume3/scripts/test.sh scriptvol: volume3 vg: vg3 md: md4 WARNING Don't store this script on an NVMe volume! /volume4/scripts/test.sh scriptvol: volume4 vg: vg4 md: md5 WARNING Don't store this script on an NVMe volume! /volume5/scripts/test.sh scriptvol: volume5 vg: vg5 md: md6 ``` I just noticed that you and I are somehow getting an extra md2 on the line after "md: md3" for volume1.
kerem commented 2026-03-11 03:02:33 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jan 6, 2024):

I just ran that test script on my DS720+ which only has 1 HDD volume and I didn't get the warning or the extra md2.

/volume1/scripts/test.sh
scriptvol: volume1
vg: vg1
md: md2
<!-- gh-comment-id:1879845246 --> @007revad commented on GitHub (Jan 6, 2024): I just ran that test script on my DS720+ which only has 1 HDD volume and I didn't get the warning or the extra md2. ``` /volume1/scripts/test.sh scriptvol: volume1 vg: vg1 md: md2 ```
kerem commented 2026-03-11 03:02:38 +03:00
Author
Owner
Copy link

@herbingk commented on GitHub (Jan 6, 2024):

I just ran that test script on my DS720+ which only has 1 HDD volume and I didn't get the warning or the extra md2.

/volume1/scripts/test.sh
scriptvol: volume1
vg: vg1
md: md2

md3 is my M.2 SSD cache
md2 is my RAID5 SATA SSD volume where the script is stored at

cat /proc/mdstat returns:

md3 : active raid1 nvme1n1p1[1] nvme0n1p1[0]
1000196800 blocks super 1.2 [2/2] [UU]

md2 : active raid5 sata1p3[0] sata3p3[2] sata4p3[3] sata5p3[4] sata6p3[5] sata2p3[1]
37453707840 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]

md1 : active raid1 sata1p2[0] sata4p2[5] sata5p2[4] sata6p2[3] sata3p2[2] sata2p2[1]
2097088 blocks [6/6] [UUUUUU]

md0 : active raid1 sata1p1[0] sata4p1[5] sata5p1[4] sata6p1[3] sata3p1[2] sata2p1[1]
8388544 blocks [6/6] [UUUUUU]

<!-- gh-comment-id:1879847707 --> @herbingk commented on GitHub (Jan 6, 2024): > I just ran that test script on my DS720+ which only has 1 HDD volume and I didn't get the warning or the extra md2. > > ``` > /volume1/scripts/test.sh > scriptvol: volume1 > vg: vg1 > md: md2 > ``` md3 is my M.2 SSD cache md2 is my RAID5 SATA SSD volume where the script is stored at **cat /proc/mdstat returns:** md3 : active raid1 nvme1n1p1[1] nvme0n1p1[0] 1000196800 blocks super 1.2 [2/2] [UU] md2 : active raid5 sata1p3[0] sata3p3[2] sata4p3[3] sata5p3[4] sata6p3[5] sata2p3[1] 37453707840 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU] md1 : active raid1 sata1p2[0] sata4p2[5] sata5p2[4] sata6p2[3] sata3p2[2] sata2p2[1] 2097088 blocks [6/6] [UUUUUU] md0 : active raid1 sata1p1[0] sata4p1[5] sata5p1[4] sata6p1[3] sata3p1[2] sata2p1[1] 8388544 blocks [6/6] [UUUUUU]
kerem commented 2026-03-11 03:02:43 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jan 6, 2024):

Your seeing the same as me. md3 is the SSD cache. md2 is the HDD array.

On my DS1821+ I get this:

# lvdisplay | grep /volume_1 | cut -d"/" -f3
vg1

And this:

# pvdisplay | grep -B 1 vg1 | grep /dev/ | cut -d"/" -f3
md3
md2

Digging a little deeper I see this:

# pvdisplay | grep -B 1 vg1
  PV Name               /dev/md3
  VG Name               shared_cache_vg1
--
  PV Name               /dev/md2
  VG Name               vg1

I believe I've found the solution. Can you try this test script to confirm it works correctly for you.
https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh

<!-- gh-comment-id:1879867091 --> @007revad commented on GitHub (Jan 6, 2024): Your seeing the same as me. md3 is the SSD cache. md2 is the HDD array. On my DS1821+ I get this: ``` # lvdisplay | grep /volume_1 | cut -d"/" -f3 vg1 ``` And this: ``` # pvdisplay | grep -B 1 vg1 | grep /dev/ | cut -d"/" -f3 md3 md2 ``` Digging a little deeper I see this: ``` # pvdisplay | grep -B 1 vg1 PV Name /dev/md3 VG Name shared_cache_vg1 -- PV Name /dev/md2 VG Name vg1 ``` I believe I've found the solution. Can you try this test script to confirm it works correctly for you. https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh
kerem commented 2026-03-11 03:02:48 +03:00
Author
Owner
Copy link

@herbingk commented on GitHub (Jan 6, 2024):

I believe I've found the solution. Can you try this test script to confirm it works correctly for you. https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh

Sure, returns no more warning:

/volume1/scripts/test.sh
scriptvol: volume1
vg: vg1
md: md2

<!-- gh-comment-id:1879878034 --> @herbingk commented on GitHub (Jan 6, 2024): > I believe I've found the solution. Can you try this test script to confirm it works correctly for you. https://github.com/007revad/Synology_enable_Deduplication/blob/test/script_on_ssd.sh Sure, returns no more warning: /volume1/scripts/test.sh scriptvol: volume1 vg: vg1 md: md2
kerem commented 2026-03-11 03:02:53 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Jan 7, 2024):

Fixed in https://github.com/007revad/Synology_enable_Deduplication/releases/tag/v1.2.17

Thank you.

<!-- gh-comment-id:1879900903 --> @007revad commented on GitHub (Jan 7, 2024): Fixed in https://github.com/007revad/Synology_enable_Deduplication/releases/tag/v1.2.17 Thank you.
kerem commented 2026-03-11 03:02:58 +03:00
Author
Owner
Copy link

@herbingk commented on GitHub (Jan 7, 2024):

It was a pleasure to me. I have to thank you for creating, maintaining and sharing these valuable scripts with us. Very much appreciated!

<!-- gh-comment-id:1880036358 --> @herbingk commented on GitHub (Jan 7, 2024): It was a pleasure to me. I have to thank you for creating, maintaining and sharing these valuable scripts with us. Very much appreciated!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
develop
test
v1.4.33
v1.4.32
v1.4.31
v1.4.30
v1.4.29
v1.4.28
v1.3.25
v1.3.24
v1.3.23
v1.3.22
v1.3.21
v1.3.19
v1.2.17
v1.2.15
v1.2.14
v1.1.13
v1.1.12
v1.0.11
v1.0.10
v1.0.9
v1.0.7
v1.0.6
v1.0.5
v1.0.4
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#188
No description provided.