https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Juan José Ivars Poquet changed:
What|Removed |Added
CC||k...@alfaexploit.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #30 from Jim Long ---
I'm happy to say that using a build as of:
stable/13-n254696-18936d3526f3
my systems are showing this issue as resolved. The exec.poststart kludge above
is no longer necessary.
@Urs, @c.tineo, @fk, what
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #29 from commit-h...@freebsd.org ---
A commit in branch releng/13.2 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=b772fe0d662650d8a517bc07f3c433486c24b347
commit b772fe0d662650d8a517bc07f3c433486c24b347
Auth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #28 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=426ed00525409d084e97dc44397722aff2cc0bb3
commit 426ed00525409d084e97dc44397722aff2cc0bb3
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #27 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=8b04c1cbfc1cb71a1ce53b3a7855f1d45866fcfb
commit 8b04c1cbfc1cb71a1ce53b3a7855f1d45866fcfb
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Allan Jude changed:
What|Removed |Added
CC||r...@freebsd.org
--- Comment #26 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #25 from Jim Long ---
For those affected by this regression who are looking for a workaround that
eliminates (or rather, automates) the need to run 'jail -m ...' on each jail
that requires access to its snapshots:
This simple c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #24 from Jim Long ---
Thanks to everyone who has contributed to the significant progress on this
issue.
It definitely feels like progress, but IMO it would be infinitely better if the
"zfs.mount_snapshot" attribute was honored
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #23 from Martin Matuska ---
(In reply to Jim Long from comment #22)
It appears that it doesn't work if that parameter is set when creating a jail.
If you set the parameter on an existing jail (e.g. with "jail -m test" or with
"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #22 from Jim Long ---
Well, no luck yet, but I think the first obstacle I have is:
# cat /etc/jail.conf
path= "/jail/$name";
test {
host.hostname = "test.example.com";
ip4.addr = "vlan3|192.168.1.50/32";
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #21 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=3d7a882488a4c1c69283614ae179df7c1d2f3a7e
commit 3d7a882488a4c1c69283614ae179df7c1d2f3a7e
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #20 from Jim Long ---
Sorry, THIS thread!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #19 from Jim Long ---
Yes, thank you, Martin. Please update that thread when this is committed and
I'll be happy to do another pull, build and test.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #18 from Allan Jude ---
(In reply to Martin Matuska from comment #17)
Thank you Martin
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #17 from Martin Matuska ---
(In reply to Jim Long from comment #16)
Looks like https://github.com/openzfs/zfs/pull/13758 was not merged into
zfs-2.1-release because of an easy to resolve conflict. I will cherry-pick it
manually
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #16 from Jim Long ---
Any update on whether this fix will be included in 13.2-RELEASE? I'm running a
PRERELEASE built yesterday, stable/13-n254268-821f1352112e and there's no sign
of improvement.
Thank you!
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Ryan Moeller changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #15 from Ry
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #14 from Jim Long ---
I would like to second the request to resolve this issue prior to 13.2-RELEASE.
My workplace uses numerous jailed Samba instances where we'd like to allow
users to access their own backups via the /.zfs/sn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #13 from Urs ---
(In reply to Robert Wing from comment #12)
Thanks for sharing this. It seems that this bug will not be fixed in 13.1.
Will it be fixed in 13.2? I hope that such regressions get more attention in
the future. We
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Robert Wing changed:
What|Removed |Added
CC||freql...@freebsd.org
--- Comment #12
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #11 from Jim Long ---
Given that this is a regression, has anyone bisected the commit history to find
which commit created this bug, and if so, could they post a link to it?
Thank you!
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #10 from Martin Matuska ---
I have the following comment from Mateusz Guzik oh this
patch:
On 29. 3. 2022 17:53, Mateusz Guzik wrote:
> whoa, stop right there.
>
> The commit at hand introduces a security problem by modifying
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #9 from c.ti...@digital-light.ch ---
Sorry to insist.
This breaks our all FreeBSD 13 + Jails + ZFS + access to snapshots from inside
the jails. To the point of being unable to deploy new jails and having to
revert to 12.3 entire
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #7 from c.ti...@digital-light.ch ---
Don't mean to be pushy. But is this fix going to be in 13.1 RELEASE? or in
which version will it be? Because this basically broke our complete stack of
FreeBSD+zfs+jails !
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #6 from c.ti...@digital-light.ch ---
Don't mean to be pushy. But is this fix going to be in 13.1 RELEASE? or in
which version will it be? Because this basically broke our complete stack of
FreeBSD+zfs+jails !
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #5 from Jim Long ---
Thank you, @rew. Please update this PR when that commit goes in to 13-STABLE.
I track that branch and can verify whether it resolves the issues my systems
are experiencing.
Thank you!
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Robert Wing changed:
What|Removed |Added
CC||allanj...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
c.ti...@digital-light.ch changed:
What|Removed |Added
CC||c.ti...@digital-light.ch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
--- Comment #2 from Jim Long ---
I can confirm numerous systems from 13.0-STABLE #0
stable/13-n245258-5b8039d5ed3e and later that do exhibit this bug.
Further, it is not necessary to set "jailed=on" none of my systems use
that. My ex
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Fabian Keil changed:
What|Removed |Added
CC||f...@fabiankeil.de
--- Comment #1 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260160
Bug ID: 260160
Summary: zfs jailed: snapshots not accessible
Product: Base System
Version: 13.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity:
33 matches
Mail list logo
