From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH zfsonlinux] add patch for spurious warning on `zfs mount -a`
Date: Thu, 2 Nov 2023 20:13:48 +0100 [thread overview]
Message-ID: <cb9079d0-3244-4ee6-a161-4ae2f1dafad5@proxmox.com> (raw)
In-Reply-To: <20231102173321.748877-1-s.ivanov@proxmox.com>
On 02/11/2023 18:33, Stoiko Ivanov wrote:
> reported in our community forum:
> https://forum.proxmox.com/threads/.135635/post-60036
The dot isn't required, but it seems the anchor # really is,
your link goes to an ancient post without that, switched it
to:
https://forum.proxmox.com/threads/135635/#post-60036
>
> the small fix was merged upstream:
> https://github.com/openzfs/zfs/pull/15468
>
> minimally tested by building with this patch and running
> `zfs mount -a` on an affected system.
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> this patch fixes a cosmetic issue, but might help keep support requests down
> a bit.
> also quickly skimmed through the other patches in upstream/master and
> salsa.debian.org - but currently don't think anything needs to be pulled in
> urgently
>
> ...runcate_shares-without-etc-exports.d.patch | 76 +++++++++++++++++++
> debian/patches/series | 1 +
> 2 files changed, 77 insertions(+)
> create mode 100644 debian/patches/0012-Fix-nfs_truncate_shares-without-etc-exports.d.patch
>
>
applied, thanks!
prev parent reply other threads:[~2023-11-02 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 17:33 [pve-devel] " Stoiko Ivanov
2023-11-02 19:12 ` [pve-devel] applied: " Thomas Lamprecht
2023-11-02 19:13 ` 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=cb9079d0-3244-4ee6-a161-4ae2f1dafad5@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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