mirror of
https://github.com/007revad/Synology_M2_volume.git
synced 2026-04-26 00:06:14 +03:00
[GH-ISSUE #151] Sharing NVME between volume and cache group? #31
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_M2_volume#31
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 @volschin on GitHub (May 5, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/151
First thank you very much for this cool script. I moved my 2x4TB nvme‘s from cache usage to volume. I had used about 400 GB as cache group before.
I have seen that there seem to be different partition types for cache group and volume. What I would really like is to share my nvme space between cache and volume usage. Is this generally possible or is this something that is technically impossible?
@007revad commented on GitHub (May 5, 2024):
DSM does not allow using a drive for a cache and a volume.
You're only the 2nd person to ever ask about it. When the first person asked I did some research and read that a cache drive is formatted differently to a drive with a storage pool.