about summary refs log tree commit diff
path: root/pkgs/os-specific/linux/zfs
AgeCommit message (Collapse)AuthorFilesLines
2024-06-07Merge pull request #311415 from toastal/zfs-2.2.4-unstable-2024-05-13Sandro1-4/+4
zfs_unstable: 2.2.4 → 2.2.4-unstable-2024-05-13
2024-06-04treewide: remove unused fetchpatch argumentsSigmanificient1-1/+1
2024-06-01zfs_unstable: 2.2.4 → 2.2.4-unstable-2024-05-29toastal1-4/+4
2024-05-03zfs_2_2: 2.2.3 -> 2.2.4Andrew Marshall1-4/+4
Now compatible with Linux 6.8. https://github.com/openzfs/zfs/releases/tag/zfs-2.2.4 Need to patch py-libzfs to support incompatible API change.
2024-05-03zfs_unstable: 2.2.3-unstable-2024-04-09 -> 2.2.4Andrew Marshall1-4/+4
No pre-release version at this moment, so use now-released 2.2.4.
2024-04-09zfs_unstable: 2.2.3-unstable-2024-03-30 → 2.2.3-unstable-2024-04-09toastal1-3/+3
2024-04-04linux_6_7: dropK9003-3/+3
2024-04-01zfs_unstable: 2.2.3-unstable-2024-03-21 → 2.2.3-unstable-2024-03-30toastal1-3/+3
2024-03-22zfsUnstable: 2.2.3-unstable-2024-02-12 → 2.2.3-unstable-2024-03-21toastal1-3/+3
Has patch to fix 6.8 issue
2024-03-01Merge pull request #291951 from amarshall/zfs-pkgs-renamingAdam C. Stephens3-5/+5
zfs: rename zfsStable -> zfs_2_2; zfsUnstable -> zfs_unstable; remove enableUnstable option in favor of package
2024-02-27nixos/zfs: Remove enableUnstable in favor of setting packageAndrew Marshall1-1/+1
This just adds complexity and confusion. Once-upon-a-time, there was no `package` and only `enableUnstable`, but now it is just confusing to have both, as it would be possible to do e.g. `package = pkgs.zfs` and `enableUnstable = true`, but then `enableUnstable` does nothing.
2024-02-27zfs_unstable: Rename from zfsUnstableAndrew Marshall2-2/+2
This matches the naming of other zfs_* pkgs.
2024-02-27zfs_2_2: Rename from zfsStableAndrew Marshall1-2/+2
The `zfs` alias already has equivalent semantics. Instead, make this like zfs_2_1 so folks who want to pin a specific release series can do so easily and clearly to have more control over when more substantial updates occur. Rename all tests to match the pkg attr they are testing.
2024-02-27zfs_2_1: 2.1.14 -> 2.1.15Alyssa Ross1-10/+4
This adds compatibility with newer kernels, which fixes nixosTests.zfs.series_2_1, which broke when the default kernel version was bumped. This means we no longer need the removeLinuxDRM option at all, but I've kept it around as a no-op so people can leave it set in case the same thing happens again in future.
2024-02-26zfs: update latestCompatibleLinuxPackagesAlyssa Ross2-16/+4
ZFS no longer tries to use GPL-only symbols on aarch64. Tested by building nixosTests.zfs.stable (modified to use Linux 6.6) and nixosTests.zfs.unstable.
2024-02-23zfs: 2.2.2 -> 2.2.3Siddhartha1-4/+4
2024-02-14zfsUnstable: 2.2.3-unstable-2024-01-26 → 2.2.3-unstable-2024-02-12toastal1-4/+4
Patch now includes compatibility for 6.8 kernels (even if ðey aren’t on offer in nixpkgs at ðis time).
2024-01-31zfsUnstable: 2.2.2 → 2.2.3-unstable-2024-01-26toastal1-4/+5
Should have patches for 6.7 compatibility
2023-11-30zfs_2_1: 2.1.13 -> 2.1.14Adam Stephens1-12/+2
2023-11-30zfsStable/zfsUnstable: 2.2.1 -> 2.2.2Adam Stephens3-58/+6
2023-11-27Merge pull request #270275 from amarshall/zfs-disable-dmu-offset-by-defaultAdam C. Stephens3-0/+52
zfs: default disable zfs_dmu_offset_next_sync to avoid data corruption
2023-11-26zfs: default disable zfs_dmu_offset_next_sync to avoid data corruptionAndrew Marshall3-0/+52
This helps mitigate a data corruption bug. This was previously defaulted to zero prior to upstream commit 05b3eb6d232009db247882a39d518e7282630753, and it is already a tunable, so doing this seems safe. Initially data corruption was thought to be introduced with v2.2, but further upstream investigation currently believes that changes in v2.2 only exacerbated the issue that already existed. A longer-term fix is likely to be https://github.com/openzfs/zfs/pull/15571, though that is not yet merged. The zfs_2_1 package has already backported that, so do not apply the tunable default change there. Positioning of `extraPatches` is to avoid merge conflicts with https://github.com/NixOS/nixpkgs/pull/269097. Patch is nearly identical to the [Gentoo][1] patch, but better patch formatting. See https://github.com/openzfs/zfs/issues/11900 See https://github.com/openzfs/zfs/issues/15526 [1]: https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-fs/zfs-kmod/files/zfs-kmod-2.2.1-Disable-zfs_dmu_offset_next_sync-tunable-by-default.patch
2023-11-26zfsUnstable: 2.2.1-unstable-2023-10-21 -> 2.2.1Jörg Thalheim1-5/+4
Signed-off-by: Jörg Thalheim <joerg@thalheim.io>
2023-11-26zfs: 2.2.0 -> 2.2.1Andrew Marshall1-4/+4
Now supports Kernel 6.6.
2023-11-24zfs: improve description and long descriptionRaito Bezarius1-1/+3
When we are building for user or kernel, we are not building a kernel module all the time.
2023-11-24zfs_2_1: init at 2.1.13Raito Bezarius4-217/+301
This re-introduces the old stable ZFS version we had in the past following the many predicted issues of ZFS 2.2.x series, that is much more stable than any further ZFS version at the moment. I am also removing myself from maintenance of any further ZFS versions as I am planning to quit ZFS maintenance at some point. In the meantime, for users like me who depend on ZFS for critical operations, here is a ZFS version that is known to work for LTS kernels.
2023-10-22zfs: add armv7 to supported platformsMajiir Paktu1-3/+3
2023-10-21zfsUnstable: 2.2.0-rc5 -> 2.2.1-unstable-2023-10-21Adam Stephens1-2/+3
2023-10-21zfs: 2.1.13 -> 2.2.0Adam Stephens2-29/+11
2023-10-14zfs: Honour NIX_BUILD_CORES in kernel buildOPNA26081-0/+8
Otherwise configuring runs some test builds with `nproc` amount of cores.
2023-10-10zfsUnstable: 2.2.0-rc4 -> 2.2.0-rc5Adam Stephens2-4/+9
2023-10-02linux_6_4: drop (EOL)Alyssa Ross1-3/+1
It's still in kernels-org.json, because even if I remove it the update script will keep putting it back, but nothing references it, and it'll be removed from that file when kernels are next updated after it's been delisted from kernel.org. linux_testing_bcachefs still needs to be updated for >6.4, so for now I've just inlined the Linux 6.4 definition in linux_testing_bcachefs's definition.
2023-09-28zfs: 2.1.12 -> 2.1.13Adam Stephens1-4/+7
2023-09-11zfsUnstable: 2.1.13 -> 2.2.0-rc4Jörg Thalheim3-40/+35
2023-08-21zfsUnstable: 2.1.12 → 2.1.13-unstable-2023-08-02toastal1-4/+7
https://github.com/openzfs/zfs/commits/zfs-2.1.13-staging With anecdote from a NixOS user that it’s working https://github.com/openzfs/zfs/pull/15125 …working for me as well as I built+booted from this commit.
2023-07-22linux_6_3: drop as EOLFabián Heredia Montiel2-11/+2
2023-06-16zfs: add option to restore kernel_neon for linux 6.2 support on aarch64Raito Bezarius2-8/+16
Introduced in https://github.com/torvalds/linux/commit/aaeca98456431a8d9382ecf48ac4843e252c07b3 with the usual disdain for ZFS. We have been there in the past with <https://www.phoronix.com/news/NixOS-Linux-5.0-ZFS-FPU-Drop> / https://github.com/NixOS/nixpkgs/pull/61076. This fixes ZFS on aarch64 until the next breakage. See https://github.com/openzfs/zfs/issues/14555 for original upstream issue.
2023-06-08zfs: 2.1.11 -> 2.1.12adisbladis1-4/+4
2023-05-26linux_6_2: dropAlyssa Ross2-8/+2
EOL
2023-05-17zfs: fix check for latestCompatibleLinuxPackagesAndreas Vollert1-2/+2
2023-05-16Merge pull request #194148 from amjoseph-nixpkgs/pr/zfs/mips-badAdam Joseph1-1/+11
zfs.meta.platforms: restrict to upstream-supported $TARGET_CPUs
2023-05-15zfs.meta.platforms: restrict to upstream-supported $TARGET_CPUsAdam Joseph1-1/+11
2023-05-15nixos/pam: enable unlocking ZFS home datasetNicola Squartini1-1/+3
2023-05-07zfs: make kernel packages overridableJörg Thalheim4-270/+282
We do not have callPackages (notice the s) for kernel packages. Hence it's not override zfs dependencies as we do not have an override function. This is fixed by splitting of the file into a generic builder function and 2 files for zfsStable and zfsUnstable.
2023-04-23Merge pull request #227279 from toastal/zfs-2.1.11Ryan Lahfa1-15/+13
zfs: 2.1.9 → 2.1.11
2023-04-20zfs: 2.1.9 → 2.1.11toastal1-15/+13
Skipping over 2.1.10 now that it was found to have possible data corruptions Release notes @ OpenZFS’s Git forge: https://github.com/openzfs/zfs/releases/tag/zfs-2.1.11
2023-04-18zfs: enable keylocation=http://Albert Peschar1-0/+4
When ZFS is built with cURL, it allows retrieving encryption keys from URLs automatically.
2023-03-28zfs: remove myself from maintainersRicardo M. Correia1-1/+1
2023-03-27zfsUnstable: make it compatible again with 6.2.8 and potentially 6.3Raito Bezarius1-0/+8
Patched from https://github.com/openzfs/zfs/pull/14668
2023-03-17zfs: add raitobezarius as a maintainerRaito Bezarius1-1/+1
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-09-03 21:14:44 +0000