From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Lendl <s.lendl@proxmox.com>
Subject: [pve-devel] applied: [PATCH zfsonlinux] Fix #5101: exports with sharenfs remain after zfs mount -a
Date: Fri, 2 Feb 2024 19:18:07 +0100 [thread overview]
Message-ID: <d6a592f5-bbc1-4bbd-8a4e-bd7840c30220@proxmox.com> (raw)
In-Reply-To: <20240129111612.431092-4-s.lendl@proxmox.com>
Am 29/01/2024 um 12:16 schrieb Stefan Lendl:
> When running `zfs mount -a`, prevent the exported datasets (with sharenfs)
> to be truncated (unexported).
> Adds tests to verify shares persist after mount -a
>
> Signed-off-by: Stefan Lendl <s.lendl@proxmox.com>
> ---
> This was merged upstream via https://github.com/openzfs/zfs/pull/15660
>
> ...do-not-truncate-shares-not-zfs-mount.patch | 131 ++++++++++++++++++
> debian/patches/series | 1 +
> 2 files changed, 132 insertions(+)
> create mode 100644 debian/patches/0012-fix-mount-do-not-truncate-shares-not-zfs-mount.patch
>
>
applied, thanks!
prev parent reply other threads:[~2024-02-02 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:16 [pve-devel] " Stefan Lendl
2024-02-02 18:18 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6a592f5-bbc1-4bbd-8a4e-bd7840c30220@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.lendl@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox