-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linux: zfs volume snapshot rename does not generate KOBJ_CHANGE, /dev/zvol/.... link is not updated #14223
Comments
I don't know if this is interesting:
|
Thanks for the report. I expect to see this fixed before Christmas. |
If there is patch we would be willing to test it. |
I had hoped that the group that last touched this infrastructure would write the patch, but they have not. I guess I will need to do it, although I cannot do it immediately. |
This is a bit of a sticking point for us at the moment and we've not managed to come up with a workaround. Is it a simple issue that someone unfamiliar with the zfs code base could resolve with a bit of guidance? |
Unfortunately, it has been somewhat difficult finding time to do this. I plan to do it, although if you would like it done faster, I suggest contacting Klara Systems to get it done. |
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
Has there been any progress on this? This is a serious blocker for a project I'm working on currently. |
I can still reproduce this problem in zfs-2.2.6. I've added a couple of printks and for the snapshot rename I can see that |
The printk I added to
If I rename a zvol with snapshots, e.g.
If I rename a snapshot , e.g.
So I suspect the problem is that |
a0bd735 removed code which prefixed
|
…ot rename `zvol_rename_minors()` needs to be given the full path not just the snapshot name. Use code removed in a0bd735 as a guide to providing the necessary values. Closes openzfs#14223 Signed-off-by: James Dingwall <james@dingwall.me.uk>
…ot rename `zvol_rename_minors()` needs to be given the full path not just the snapshot name. Use code removed in a0bd735 as a guide to providing the necessary values. Closes openzfs#14223 Signed-off-by: James Dingwall <james@dingwall.me.uk>
…ot rename `zvol_rename_minors()` needs to be given the full path not just the snapshot name. Use code removed in a0bd735 as a guide to providing the necessary values. Closes openzfs#14223 Signed-off-by: James Dingwall <james@dingwall.me.uk>
…ot rename `zvol_rename_minors()` needs to be given the full path not just the snapshot name. Use code removed in a0bd735 as a guide to providing the necessary values. Closes openzfs#14223 Signed-off-by: James Dingwall <james@dingwall.me.uk>
…ename After renaming a snapshot with 'snapdev=visible' ensure that the /dev entries are updated to reflect the rename. Signed-off-by: James Dingwall <james@dingwall.me.uk>
…ot rename `zvol_rename_minors()` needs to be given the full path not just the snapshot name. Use code removed in a0bd735 as a guide to providing the necessary values. Closes openzfs#14223 Signed-off-by: James Dingwall <james@dingwall.me.uk>
…ename After renaming a snapshot with 'snapdev=visible' ensure that the /dev entries are updated to reflect the rename. Signed-off-by: James Dingwall <james@dingwall.me.uk>
`zvol_rename_minors()` needs to be given the full path not just the snapshot name. Use code removed in a0bd735 as a guide to providing the necessary values. Add ZTS check for /dev changes after snapshot rename. After renaming a snapshot with 'snapdev=visible' ensure that the /dev entries are updated to reflect the rename. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: James Dingwall <james@dingwall.me.uk> Closes openzfs#14223 Closes openzfs#16600
System information
Describe the problem you're observing
When a volume snapshot is renamed
zfs rename pool/volume@snap pool/volume@other
the corresponding /dev/zvol/... link is not updated. Runningudevadm monitor
shows no uevent is generated for the action. If the volume (not snapshot) is renamed then uevents are generated and all links are correct.Describe how to reproduce the problem
The expected result is that the @1 symlink is removed and an @3 one is created.
Include any warning/errors/backtraces from the system logs
No messages are recorded in syslog or kern.log which indicate an error.
The text was updated successfully, but these errors were encountered: