follows commit e1e64f07af5c4ca2a313625a15c24e4ad6fb42f1 in debian
upstream [0].
context from upstream's commit message:
- arc_summary and zilstat do not require privilege.
- arcstat does not need root, but the name is taken by nordugrid-arc-client.
- dbufstat needs root permission to read /proc/sp
This patchset updates ZFS to 2.2.5 which was released two weeks ago [0]
The changes don't look too scary, but could prevent a few issues in not so
common use-cases for us e.g.:
https://github.com/openzfs/zfs/pull/16359/commits/4d2f7f9839d12708417457cd57cf43d15cae5e92
https://github.com/openzfs/zfs/
When initially packaging libzfsbootenv1linux a .install file was
commited in addtion to the .install.in (which contains the proper path
with the multiarch component). This wasn't noticed during building
because the .install got clobbered while building
Fixes: fd0cc4becda91c46991e723ae6f0b08dcdf661
follows commit 902967808693510631a198414dc57dc4ca564afe in debian
upstream [0], which was done to support usrmerge
[0] https://salsa.debian.org/zfsonlinux-team/zfs
Signed-off-by: Stoiko Ivanov
---
debian/libnvpair3linux.install.in | 2 +-
debian/libpam-zfs.install
patches did not need adaptation
Signed-off-by: Stoiko Ivanov
---
upstream | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/upstream b/upstream
index 25665920..33174af1 16
--- a/upstream
+++ b/upstream
@@ -1 +1 @@
-Subproject commit 2566592045780e7be7afc899c2496b1ae3af4f4d
to raise awareness for the changed paths (NEWS entries get displayed
when installing updates).
follows commit 20e286d2f5c8752ac1372cd084729147cf276f3f in debian
upstream [0].
[0] https://salsa.debian.org/zfsonlinux-team/zfs
Signed-off-by: Stoiko Ivanov
---
debian/NEWS | 13 +
1 fil
On Mon, Aug 19, 2024 at 12:32:09PM GMT, Christoph Heiss wrote:
> On Tue, Jul 23, 2024 at 04:31:35PM GMT, Aaron Lauterer wrote:
> > In my tests, with secure boot disabled, it failed to parse the
> > run-env-info.json because the Perl code wrote it this way:
> >
> > "secure_boot":""
> >
> > And it cu
Tested these two patches on PVE 8 and they work as advertised, fixing
the problem described in [1]. So, consider this
Tested-by: Hannes Laimer
code also looks good, but I don't think R-b is warranted here.
[1] https://bugzilla.proxmox.com/show_bug.cgi?id=3873
_
--- Begin Message ---
Hello Team,
I am new to the community, and I have few basic questions that I would like to
clarify:
1. Can you share details on how to develop a storage plugin for Proxmox?
2. Can you also share some more details how do achieve replication of
virtual machines betwee
