Date: Sun, 12 Apr 2026 03:16:30 +0000 From: Kyle Evans <kevans@FreeBSD.org> To: src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-branches@FreeBSD.org Subject: git: ebf890d48f51 - stable/15 - rc: run the zfs rc script before tmp Message-ID: <69db0e8e.46bd2.27e6b4f3@gitrepo.freebsd.org>
index | next in thread | raw e-mail
The branch stable/15 has been updated by kevans: URL: https://cgit.FreeBSD.org/src/commit/?id=ebf890d48f51615ffacd32b3ed5c154a51392754 commit ebf890d48f51615ffacd32b3ed5c154a51392754 Author: Kyle Evans <kevans@FreeBSD.org> AuthorDate: 2026-02-03 03:21:42 +0000 Commit: Kyle Evans <kevans@FreeBSD.org> CommitDate: 2026-04-12 03:15:11 +0000 rc: run the zfs rc script before tmp The tmp rc script has much the same problem that the var does: it wants to test if /tmp is writable, and mount a tmpfs if it's not. This means that we actually want our zfs datasets mounted first, because we might have a /tmp dataset that changes the story. The ordering problem is particularly noticable with a r/o zfs root, since the write test will fail and we'll mount a tmpfs that later gets covered by our /tmp dataset. If that /tmp dataset inherited readonly, then we're still in trouble. This also fixes `tmpmfs=yes`, which would again get covered by a zfs dataset with the existing ordering. Reviewed by: des (cherry picked from commit d3f21856aa72c28408660ed40ce76bbd0716a991) --- libexec/rc/rc.d/zfs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libexec/rc/rc.d/zfs b/libexec/rc/rc.d/zfs index f88f65c2ec18..99156332e47b 100755 --- a/libexec/rc/rc.d/zfs +++ b/libexec/rc/rc.d/zfs @@ -4,7 +4,7 @@ # PROVIDE: zfs # REQUIRE: zfsbe -# BEFORE: FILESYSTEMS var +# BEFORE: FILESYSTEMS tmp var . /etc/rc.subrhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69db0e8e.46bd2.27e6b4f3>