Date: Mon, 06 Feb 2023 18:47:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260160] zfs jailed: snapshots not accessible Message-ID: <bug-260160-227-xcZ0BVQ5lg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260160-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260160-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260160 --- Comment #22 from Jim Long <freebsd-bugzilla@umpquanet.com> --- Well, no luck yet, but I think the first obstacle I have is: # cat /etc/jail.conf path =3D "/jail/$name"; test { host.hostname =3D "test.example.com"; ip4.addr =3D "vlan3|192.168.1.50/32"; allow.raw_sockets =3D 1; exec.clean; exec.system_user =3D "root"; exec.jail_user =3D "root"; exec.start +=3D "/bin/sh /etc/rc"; exec.stop =3D "/bin/sh /etc/rc.shutdown"; exec.consolelog =3D "/var/log/jail_test.log"; mount.devfs; # When this is supported, that likely means the jail vs. snapshot bug has # been fixed: zfs.mount_snapshot=3D1; allow.set_hostname =3D 0; allow.sysvipc =3D 0; } But the jail is not seeing the mount_snapshot attribute: # service jail restart; jexec test sysctl -a | grep zfs\.mount Stopping jails: test. Starting jails: test. security.jail.param.zfs.mount_snapshot: 0 Without that attribute set, then of course: # jexec test ls -l /.zfs/snapshot/prior-to-installkernel ls: /.zfs/snapshot/prior-to-installkernel: Operation not permitted What am I overlooking? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260160-227-xcZ0BVQ5lg>