You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When migrating user dataset from an old system to the new one. It is not updated by zsys.
To Reproduce
use zfs send/receive to move the dataset. Then rename mount directory or remove the current dataset so that it will not conflict. verify that the mount directory in the received dataset is correct.
zsysctl save - v
should generate zsys snapshot. It does not.
I get the following error.
INFO Requesting to save state for user "dror"
INFO Couldn't find any association for user dataset rpool/USERDATA/dror_zo0whd
Expected behavior
a zsys snapshot should be generated.
This is not a workaround, but the actual implementation :)
I would rephrase the bug to something like a feature request: "Please include a command to include new user datasets" (this would ensure the dataset is set in /USERDATA/ + proceed the same tagging as you did). Mind retitling it?
odror
changed the title
zsys ignores a newly migrated user dataset that replaced the default installed dataset.
Feature Request: Let zsys manage a newly migrated user dataset that replaced the default installed dataset
Mar 25, 2021
Describe the bug
When migrating user dataset from an old system to the new one. It is not updated by zsys.
To Reproduce
use zfs send/receive to move the dataset. Then rename mount directory or remove the current dataset so that it will not conflict. verify that the mount directory in the received dataset is correct.
zsysctl save - v
should generate zsys snapshot. It does not.
I get the following error.
INFO Requesting to save state for user "dror"
INFO Couldn't find any association for user dataset rpool/USERDATA/dror_zo0whd
Expected behavior
a zsys snapshot should be generated.
ubuntu-bug zsys --save=/tmp/report
/tmp/report
content:Screenshots
None
Installed versions:
Additional context
None
The text was updated successfully, but these errors were encountered: