c/zfsonlinux
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
00036e5a6e
zfsonlinux/debian/patches/series

19 lines
962 B
Plaintext
Raw Normal View History

zfs/debian: add packaging files based on Debian's packaging work, but simplified: - no DKMS - no dracut - no udebs and remove old patches which were based on top of Debian's packaging. Reviewed-by: Stoiko Ivanov <s.ivanov@proxmox.com> Tested-by: Stoiko Ivanov <s.ivanov@proxmox.com> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2019-01-30 17:26:24 +03:00
0001-Check-for-META-and-DCH-consistency-in-autoconf.patch
rebase patches on top of zfs-0.8.0 rebase done with export-patchqueue and adapted to new 0.8 release Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
2019-05-24 00:11:30 +03:00
0002-always-load-ZFS-module-on-boot.patch
0003-Fix-the-path-to-the-zed-binary-on-the-systemd-unit.patch
update submodule and patches to 0.8.2 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2019-09-28 09:12:00 +03:00
0004-import-with-d-dev-disk-by-id-in-scan-service.patch
0005-Enable-zed-emails.patch
Preserve /etc/zfs/zed.d configuration on upgrade Of the zedlet scripts shipped by upstream, a subset are enabled by default, by creating symlinks in /etc/zfs/zed.d. These symlinks are shipped in the zfs-zed package. dpkg, however, does not support conffile handling of symlinks, and therefore any changes (removals) to the symlinks are not preserved on package upgrade. To address this policy violation, we: 1. During package build, create a list of enabled-by-default zedlets, instead of creating symlinks. 2. On package removal, identify all enabled-by-default zedlets whose symlinks do not exist (i.e., were removed by the user). This is done by creating "whiteout" links to /dev/null in their place). 3. On package installation, create links to enabled-by-default zedlets UNLESS there is already a file there (i.e., abort if there is a whiteout link). 4. We also clean up broken symlinks to removed zedlets at package postinst. (cherry picked and adapted from 5cee380324d74e640d5dd7a360faba3994c8007f [0]) [0] https://salsa.debian.org/zfsonlinux-team/zfs.git Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
2020-03-20 19:28:43 +03:00
0006-dont-symlink-zed-scripts.patch
update ZFS submodule to 2.1.11 and refresh patches Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2023-04-20 10:26:09 +03:00
0007-Add-systemd-unit-for-importing-specific-pools.patch
0008-Patch-move-manpage-arcstat-1-to-arcstat-8.patch
update submodule and patches for 2.2.0 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2023-10-15 13:08:06 +03:00
0009-arc-stat-summary-guard-access-to-l2arc-MFU-MRU-stats.patch
fix #5014 reenable blk-mq optimization While I think the huge performance optimization was at some point not really that huge in practice - the feature sounds like it would benefit our use-case: https://github.com/openzfs/zfs/pull/13148 currently the feature is disabled in 2.2.0 (see the second patch), because of the issues addressed by the first patch Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com> Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2023-10-25 12:13:11 +03:00
0010-zvol-Remove-broken-blk-mq-optimization.patch
0011-Revert-zvol-Temporally-disable-blk-mq.patch
add patch for spurious warning on `zfs mount -a` reported in our community forum: 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>
2023-11-02 20:33:21 +03:00
0012-Fix-nfs_truncate_shares-without-etc-exports.d.patch
backport work-around for UBSAN-errors with variable arrays Link: https://github.com/openzfs/zfs/pull/15510 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2023-11-12 13:30:28 +03:00
0013-Workaround-UBSAN-errors-for-variable-arrays.patch
ensure vdev_stat struct layout compat betweem 2.1 and 2.2 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2023-11-12 17:59:55 +03:00
0014-zpool-status-tighten-bounds-for-noalloc-stat-availab.patch
pick bug-fixes staged for 2.2.1 ZFS 2.2.1 is currently being prepared, but the 3 patches added here seem quite relevant, as the might cause dataloss/panics on setups which run `zpool upgrade`. See upstreams discussion for 2.2.1: https://github.com/openzfs/zfs/pull/15498/ and the most critical issue: https://github.com/openzfs/zfs/pull/15529 finally: https://github.com/openzfs/zfs/commit/459c99ff2339a4a514abcf2255f9b3e5324ef09e should not hurt either the change to the UBSAN patch (0013) is unrelate, cosmetic only and happened by running export-patchqueue. Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
2023-11-17 17:03:02 +03:00
0015-Fix-block-cloning-between-unencrypted-and-encrypted-.patch
0016-Add-a-tunable-to-disable-BRT-support.patch
0017-zfs-2.2.1-Disable-block-cloning-by-default.patch
cherry-pick fix for data corruption cherry-picked from 2.2.0-staging, fixing https://github.com/openzfs/zfs/issues/15526 Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2023-11-29 11:18:39 +03:00
0018-dnode_is_dirty-check-dnode-and-its-data-for-dirtines.patch
Reference in New Issue Copy Permalink