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
After upgrading ZFS to a version which includes a fix to propogate dataset properties into mount options (commit 34118ea), automounts of snapshots will hang indefinitely. This problem is only present until the system is rebooted into the updated kernel (with the new ZFS version).
The following text from the commit indicates the reason for this issue:
Furthermore, don't run mount.zfs(8) helper for automounting snapshot.
The above change to make mount.zfs(8) to call 'zfs_mount_at'
apparently caused it to trigger an automount for the snapshot
directory. When the helper was invoked as a result of a snapshot
automount, an infinite recursion will occur.
The fix for this issue that was included in the commit was to add the -i flag to mounts requested from zfsctl_snapshot_mount in the kernel. This prevents mount.zfs from being invoked. However, before the new kernel is running we will not have this flag present and the userland changes made by this commit will cause this issue to occur.
Describe how to reproduce the problem
See above description of the problem.
Include any warning/errors/backtraces from the system logs
Here is an example of the issue as it manifests in the kernel logs:
System information
Describe the problem you're observing
After upgrading ZFS to a version which includes a fix to propogate dataset properties into mount options (commit
34118ea), automounts of snapshots will hang indefinitely. This problem is only present until the system is rebooted into the updated kernel (with the new ZFS version).
The following text from the commit indicates the reason for this issue:
The fix for this issue that was included in the commit was to add the
-i
flag to mounts requested fromzfsctl_snapshot_mount
in the kernel. This preventsmount.zfs
from being invoked. However, before the new kernel is running we will not have this flag present and the userland changes made by this commit will cause this issue to occur.Describe how to reproduce the problem
See above description of the problem.
Include any warning/errors/backtraces from the system logs
Here is an example of the issue as it manifests in the kernel logs:
The text was updated successfully, but these errors were encountered: