Skip to content
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

Snapshot automount fails under chroot #3778

Closed
lazy404 opened this issue Sep 14, 2015 · 4 comments
Closed

Snapshot automount fails under chroot #3778

lazy404 opened this issue Sep 14, 2015 · 4 comments
Milestone

Comments

@lazy404
Copy link

lazy404 commented Sep 14, 2015

Sep 14 18:31:36 www kernel: WARNING: Unable to automount /.zfs/snapshot/test/wwwpool/lazydev_zfstest@test: 512

wwwpool is mounted under /home/www, the process is chrooted at /home/www/lazydev_zfstest

full_path should be /home/www/lazydev_zfstest/.zfs/snapshot/test but is /.zfs/snapshot/test
https://github.com/zfsonlinux/zfs/blob/master/module/zfs/zfs_ctldir.c#L691
called by
https://github.com/zfsonlinux/zfs/blob/master/module/zfs/zfs_ctldir.c#L1069

using d_absolute_path() fixed the issue but it isn't normally exported

@behlendorf behlendorf added this to the 0.7.0 milestone Sep 21, 2015
@behlendorf
Copy link
Contributor

@lazy404 as of 0.6.5 we have another way to tackle this. We could use zfsctl_snapshot_path_objset() to construct the full path when the path generated by zfsctl_snapshot_path() fails. This function was added to handle the NFS auto-mount case which is similar to the chroot case. That way we don't need to depend on d_absolute_path() which as you point out isn't always available.

@behlendorf
Copy link
Contributor

@lazy404 are you still observing this with recent 0.6.5.x releases?

@lazy404
Copy link
Author

lazy404 commented Apr 6, 2016

It failed with some earlier 0.6.5.x releases but it was gracefull,
i will check with the last one

@behlendorf behlendorf modified the milestones: 0.8.0, 0.7.0 Jul 15, 2016
@behlendorf
Copy link
Contributor

This issue was resolved in the 0.7 series.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants