Dataset not remounted after rollback of parent directory #11511
Labels
Status: Stale
No recent activity for issue
Status: Triage Needed
New issue which needs to be triaged
Type: Defect
Incorrect behavior (e.g. crash, hang)
System information
Describe the problem you're observing
It looks like a dataset mounted as
A/B
will no longer be accessible (or mounted at all) ifA
is rolled-back from a snapshot. Trying to force a remount viaset mountpoint=A/B-foobar
will not work. An effective workaround is first settingmountpount=none
and thenmountpoint=A/B
again.Describe how to reproduce the problem
The following steps come from the logs of my system. It is likely that some of these steps are not necessary to reproduce the issue.
These are the relevant datasets and snapshots present in the system
First, the
parent/.sub
dataset must be remounted somewhere else and the stray mountpoint removed.The issue start when a snapshot of the parent directory is rolled back:
A this point, one expects
/srv/parent/.subX
to still be mounted/available. but it is not.Remounting the
.sub
dataset with another mountpoint does not help.A workaround that works is first unmounting the dataset and then remounting it
Include any warning/errors/backtraces from the system logs
None that I could find. It is a bit worrysome that the
set mountpoint
operation is silently failing (from the point of view of the user) without any kind of feedback.The text was updated successfully, but these errors were encountered: