From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup-restore-image] kernel: enable codepage 437 for vfat support
Date: Tue, 26 Nov 2024 14:52:50 +0100 [thread overview]
Message-ID: <20241126145250.64a9ba4d@rosa.proxmox.com> (raw)
In-Reply-To: <4cf62736-6394-482a-9f30-0621b6405ed3@proxmox.com>
On Tue, 26 Nov 2024 13:30:17 +0100
Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:
> Am 26.11.24 um 13:26 schrieb Fabian Grünbichler:
>
> Yes, I would go directly to 6.11 once we got a new tag from ubuntu and
> after the releases, maybe ZFS 2.3 is done by then, which could be also
> nice to have then (albeit I did not check if that would provide new
> pool-features that 2.2 does not understands)
sounds sensible - the issue has been around for at least one year (change
to kernel 6.5) - and I'm not aware that anyone has run into it yet, apart
from my test - so no particular rush there
as for ZFS 2.3 - I assume that fast dedup[0] and long-names [1] might be
features that are not read-only compatible (but did not check the code
closely) - for raid-Z expansion - the pull-request mentions that it's not
read-only compatible.
I'll try to update the kernel+zfs here when looking into ZFS-2.3.0
[0] https://github.com/openzfs/zfs/discussions/15896
[1] https://github.com/openzfs/zfs/pull/15921
[2] https://github.com/openzfs/zfs/pull/15022
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-11-26 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 12:03 [pbs-devel] [PATCH] " Stoiko Ivanov
2024-11-26 12:26 ` [pbs-devel] [PATCH proxmox-backup-restore-image] " Fabian Grünbichler
2024-11-26 12:30 ` Thomas Lamprecht
2024-11-26 13:52 ` Stoiko Ivanov [this message]
2024-11-26 13:42 ` Stoiko Ivanov
2024-11-26 13:51 ` Fabian Grünbichler
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=20241126145250.64a9ba4d@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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