| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 1000-dont-symlink-zed-scripts.patch | track default symlinks, instead of symlinking=================================================================== | invalid | ||||
| 1001-Prevent-manual-builds-in-the-DKMS-source.patch | Block manual building in the DKMS source tree. To avoid messing up future DKMS builds and the zfs installation, block manual building of the DKMS source tree. =================================================================== |
unknown | not-needed | ubuntu | 2017-10-06 | |
| 1002-Check-for-META-and-DCH-consistency-in-autoconf.patch | check for META and dch consistency in autoconf=================================================================== | invalid | ||||
| 1003-relocate-zvol_wait.patch | relocate the executable path=================================================================== | invalid | ||||
| 1005-enable-zed.patch | Enable zed emails The OpenZFS event daemon monitors pools. This patch enables the email sending function by default (if zed is installed). This is consistent with the default behavior of mdadm. =================================================================== |
Richard Laager <rlaager@wiktel.com> | not-needed | |||
| 1006-zed-service-bindir.patch | Fix the path to the zed binary on the systemd unit. We install zed into /usr/sbin manually meanwhile the upstream default is installing it into /sbin. Ubuntu packages also install zed to /usr/sbin, but they ship their own zfs-zed unit. =================================================================== |
Chris Dos <chris@chrisdos.com> | no | debian | ||
| 1007-dkms-pkgcfg.patch | =================================================================== | no | ||||
| 2100-zfs-load-module.patch | explicitly load the ZFS module via systemd service=================================================================== | Ubuntu developers | no | |||
| 3100-remove-libzfs-module-timeout.patch | Reduce the timeout to zero seconds when running in a container (LP: #1760173) When inside a lxd container with zfs storage, zfs list or zpool status appears to hang, no output for 10 seconds. Check if we are inside a container and set the timeout to zero in this specific case. |
no | ||||
| force-verbose-rules.patch | force libtool to produce verbose output=================================================================== | Mo Zhou | invalid | |||
| 4620-zfs-vol-wait-fix-locked-encrypted-vols.patch | don't wait for links when volume has property keystatus=unavailable zfs-volume-wait.service systemd unit does not start if the encrypted zvol is locked. The /sbin/zvol_wait should not wait for links when the volume has property keystatus=unavailable. This patch fixes this issue =================================================================== |
James Dingwall | no | upstream | ubuntu | 2020-07-22 |
| move-arcstat-1-to-8.patch | commit c999ab77f8dad6c6655007baebe9c7992d6fe206 Move arcstat(1) to arcstat(8) to avoid conflict with binary package nordugrid-arc-client. We regenerate Makefile.in, so we don't have to modify them explicitly here. =================================================================== |
Mo Zhou <cdluminate@gmail.com> | no | 2021-01-15 | ||
| skip-on-PREEMPT_RT.patch | do not attempt to build the modules on PREEMPT_RT kernels =================================================================== |
Andreas Beckmann <anbe@debian.org> | yes | debian upstream | ||
| zzstd-version-bump.patch | Bump zzstd.ko module version number. All modules are going to be merged into one upstream soon. At the moment all other modules increase with every build, but zzstd one. Append zfs package version to zzstd module version number, to make dkms module versions higher than kernel prebuilt ones. =================================================================== |
Dimitri John Ledkov <dimitri.ledkov@canonical.com> | no | |||
| cross-compile.patch | Fix cross-compile of the dkms module. =================================================================== |
Dimitri John Ledkov <dimitri.ledkov@canonical.com> | no | |||
| 0004-Increase-default-zfs_scan_vdev_limit-to-16MB.patch | [PATCH] Increase default zfs_scan_vdev_limit to 16MB For HDD based pools the default zfs_scan_vdev_limit of 4M per-vdev can significantly limit the maximum scrub performance. Increasing the default to 16M can double the scrub speed from 80 MB/s per disk to 160 MB/s per disk. This does increase the memory footprint during scrub/resilver but given the performance win this is a reasonable trade off. Memory usage is capped at 1/4 of arc_c_max. Note that number of outstanding I/Os has not changed and is still limited by zfs_vdev_scrub_max_active. Closes #14428 |
Brian Behlendorf <behlendorf1@llnl.gov> | no | 2023-01-24 | ||
| 0005-Increase-default-zfs_rebuild_vdev_limit-to-64MB.patch | [PATCH] Increase default zfs_rebuild_vdev_limit to 64MB When testing distributed rebuild performance with more capable hardware it was observed than increasing the zfs_rebuild_vdev_limit to 64M reduced the rebuild time by 17%. Beyond 64MB there was some improvement (~2%) but it was not significant when weighed against the increased memory usage. Memory usage is capped at 1/4 of arc_c_max. Additionally, vr_bytes_inflight_max has been moved so it's updated per-metaslab to allow the size to be adjust while a rebuild is running. Closes #14428 |
Brian Behlendorf <behlendorf1@llnl.gov> | no | 2023-01-24 | ||
| 0006-rootdelay-on-zfs-should-be-adaptive.patch | [PATCH] rootdelay on zfs should be adaptive The 'rootdelay' boot option currently pauses the boot for a specified amount of time. The original intent was to ensure that slower configurations would have ample time to enumerate the devices to make importing the root pool successful. This, however, causes unnecessary boot delay for environments like Azure which set this parameter by default. This commit changes the initramfs logic to pause until it can successfully load the 'zfs' module. The timeout specified by 'rootdelay' now becomes the maximum amount of time that initramfs will wait before failing the boot. Closes #14430 |
George Wilson <george.wilson@delphix.com> | no | 2023-02-02 | ||
| 0009-zdb-zero-pad-checksum-output.patch | [PATCH] zdb: zero-pad checksum output The leading zeroes are part of the checksum so we should show them. Closes #14464 |
=?UTF-8?q?Rob=20N=20=E2=98=85?= <robn@despairlabs.com> | no | 2023-02-08 | ||
| 0010-zdb-zero-pad-checksum-output-follow-up.patch | [PATCH 01/13] zdb: zero-pad checksum output follow up Apply zero padding for checksums consistently. The SNPRINTF_BLKPTR macro was not updated in commit ac7648179c8 which results in the `cli_root/zdb/zdb_checksum.ksh` test case reliably failing. Closes #14497 |
Brian Behlendorf <behlendorf1@llnl.gov> | no | 2023-02-15 |