On 04.01.22 17:44, Roland wrote:
>>> +sub phase2_start_remote_cluster {
>>> + my ($self, $vmid, $params) = @_;
>>> +
>>> + die "insecure migration to remote cluster not implemented\n"
>>> + if $params->{migrate_opts}->{type} ne 'websocket';
>>> +
>>> + my $remote_vmid = $self->{opts}-
when having selected 'off', the next start of the window has both
radiobuttons selected and no change is possible anymore. It seems that
the 'checked: true' triggers only after the 'init' function.
So instead remove the 'checked: true', and add the default in the init
function.
Signed-off-by: Dom
2.0.7 contains a few commits which might affect our users e.g.:
`ZFS send/recv with ashift 9->12 leads to data corruption`
the second commit is a cherry-pick from our current master
(abigail failures should not cause the build to abort)
built and booted the kernel on one of our hardware-testhosts
Signed-off-by: Stoiko Ivanov
---
debian/patches/0005-Enable-zed-emails.patch | 2 +-
debian/patches/0007-Use-installed-python3.patch | 6 +++---
upstream| 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/debian/patches/0005-Enable-ze
From: Aron Xu
(cherry picked from debian upstream [0]
commit 5ae98b5499022c2c127d546a7b5aeb906f6f2a6b)
[0] https://salsa.debian.org/zfsonlinux-team/zfs
Signed-off-by: Stoiko Ivanov
---
debian/rules | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/rules b/debian/rules
On 11.01.22 11:26, Dominik Csapak wrote:
> when having selected 'off', the next start of the window has both
> radiobuttons selected and no change is possible anymore. It seems that
> the 'checked: true' triggers only after the 'init' function.
>
> So instead remove the 'checked: true', and add th
On 01.01.22 21:06, Nils Sandmann wrote:
> Signed-off-by: Nils Sandmann
> ---
> src/dns-challenge-schema.json | 4
> 1 file changed, 4 insertions(+)
>
>
applied, many thanks for your contribution!
___
pve-devel mailing list
pve-devel@lists.proxm
the changes to zvol_open added to 2.1.2 (for coping with kernel
changes in 5.13) seem to have introduced a lock order inversion [0].
(noticed while reviewing the 2.0.6->2.0.7 changes (the patch was
applied after 2.1.2 was already tagged)
[0] https://github.com/openzfs/zfs/pull/12863
Signed-off-by
On 11.01.22 16:39, Stoiko Ivanov wrote:
> the changes to zvol_open added to 2.1.2 (for coping with kernel
> changes in 5.13) seem to have introduced a lock order inversion [0].
>
> (noticed while reviewing the 2.0.6->2.0.7 changes (the patch was
> applied after 2.1.2 was already tagged)
>
> [0] h
hi all!
i recently was playing with the ZOL module parameters, while tuning compression
algos for my filer, and ran into a scenario that would be valuable knowledge
here as well (i think)
not to go down the rabbit hole of why one might or might not want to do this
too far, but TLDR: recordsize
10 matches
Mail list logo
