Change:
<ins> From b8f9827fc4de9296c7a6f5e6fdac46e070cd6cb4 Mon Sep 17 00:00:00 2001 From: Igor Pashev <pashev.igor@gmail.com> Date: Sat, 1 Nov 2014 18:10:05 +0300 Subject: [PATCH] Fixed crash on Linux when stack size is unlimited --- pxz.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/pxz.c b/pxz.c index 9cb843e..52713e2 100644 --- a/pxz.c +++ b/pxz.c @@ -65,7 +65,7 @@ FILE **ftemp; char str[0x100]; char buf[BUFFSIZE]; char *xzcmd; -size_t xzcmd_max; +const size_t xzcmd_max = 10240; unsigned opt_complevel = 6, opt_stdout, opt_keep, opt_threads, opt_verbose; unsigned opt_force, opt_stdout; @@ -243,9 +243,12 @@ int main( int argc, char **argv ) { lzma_filter filters[LZMA_FILTERS_MAX + 1]; lzma_options_lzma lzma_options; -	xzcmd_max = sysconf(_SC_ARG_MAX); page_size = sysconf(_SC_PAGE_SIZE); xzcmd = malloc(xzcmd_max); +	if (!xzcmd) { +		fprintf(stderr, "Failed to allocate %lu bytes for xz command.n", xzcmd_max); +		return -1; +	} snprintf(xzcmd, xzcmd_max, XZ_BINARY); parse_args(argc, argv); </ins>

Discussion:
Was about to update my nix-store a Fedora 25 workstation: $ nix-channel --update downloading Nix expressions from ‘’... downloading ‘’... [8991/9145 KiB, 640.3 KiB/s] $ nix-env -u error: removing extended attribute ‘system.nfs4acl’ from ‘/nix/store/ijxblasjbl4l53gd3cg3q49ci8nh6wj1-env-’: Input/output error This used to work for years. The store is located on an NFSv4 mount served over network. Its location is `. # set up nix and nixpkgs; then $ nix-channel --update $ nix-env -u System: (NixOS: , Ubuntu/Fedora: , ...) $ uname -a Linux drift.m.i2n 4.12.11-200.fc25.x8664 SMP Fri Sep 8 11:44:51 UTC 2017 x8664 x8664 x8664 GNU/Linux Nix version: (run ) $ nix-env --version nix-env (Nix) 1.11.14 Nixpkgs version: (run ) $ nix-instantiate --eval '<nixpkgs' -A lib.nixpkgsVersion "18.03pre114739." Sandboxing enabled: (run ) Does not apply: Not NixOS.
Probably caused by NixOS/nix
Looks like. Anything I can do?
We can probably ignore , as with , but we'd have to be sure that this leaves no ACLs behind...
Could this be made configurable? I imagine other situations may arise where users need to whitelist attributes because of an exotic setup.
Just having the same problem on a Lustre file system:
Hello, Any news? Because of that error I can't even install nix.
If you are willing to compile it manually, you can apply the patch supplied by phi-gamma. I've had success with that solution. After bootstrapping, the following might be what you need:
: Thank you for the tip, but do you have any idea why this fix is not included upstream?
I'm having this issue in nix 2.0.2, which I just built manually from source.

I'm confused as to how to apply the workaround mentioned (since I'm just learning how to use nix); it looks like after dropping that file (in my home directory? Or somewhere in my nix store or state directories?) I need to use nix to rebuild nix. Is that likely to work if I can't update the channels? And how would I go about doing that? EDIT: I applied the patch at by manually patching the nix source and rebuilding. Now I have a new error to solve.
I'm having this error in Nix 2.1.3 with a CephFS filesystem: I'd also appreciate if this were made configurable, since indiscriminately removing xattrs from files can cause problems in unusual setups.
Is this error related ?
Is there an easier workaround like granting the chattr rights to the user, who does the single-user-installation of in ubuntu? does not work.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
Still important to me. I have the same issue but with .
Still important to me. I can't install nix because of this error. Is there any workaround I can do when installing?
Note the simple workaround of using NFSv3. (Worked when I ran into it just now.)
Linux kernel NFS client code disables removing system.nfs4_acl xattr