Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zfs_unstable: 0.8.0-rc3 -> 2019-03-29 #58553

Closed
wants to merge 1 commit into from
Closed

Conversation

sjau
Copy link

@sjau sjau commented Mar 29, 2019

Motivation for this change

Adding ssd trim patch to zfs unstable: openzfs/zfs#8419

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

Copy link
Member

@grahamc grahamc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't feel good about getting off release candidates and applying patches from funny domains for TRIM

@sjau
Copy link
Author

sjau commented Mar 29, 2019

Feel free to host the updated patch file yourself. I fail to see why you call it a "funny" domain.

Also, afaik, TRIM has always been planned to be included into 0.8.0. Since it's zfs unstable I see no difference to go to latest git master.

isUnstable = true;

extraPatches = [
# in case this gets out of date, just send Mic92 a pull request!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do that instead of deleting the comment.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On a related note, would you be interested in upstreaming this a version of this patch? We have an opportunity to add NixOS to the ZFSoL CI / build farm, and I think not requiring patches would be a step in that direction.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do that instead of deleting the comment.

This just got deleted by accident.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@grahamc sounds good to me. Do you have some contacts in that direction?

@sjau
Copy link
Author

sjau commented Mar 30, 2019

I guess there's no interest.

@sjau sjau closed this Mar 30, 2019
@ElvishJerricco
Copy link
Contributor

I was interested. The trim patch was merged to master, was it not? Could we not just point to master instead of hosting patches?

@grahamc I do like being on a release candidate, but once 0.8 is released, zfsUnstable will have nowhere to point but master, right? It is a little odd to me that zfsUnstable currently points to a version that's over two months old; I think monthly updates would be considered normal for the unstable moniker.

@sjau sjau deleted the zfs_trim branch September 20, 2019 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants