Setting permissions freezes at "Reticulating Splines"

[victorhooi]

Hi,

I am trying to set ACLs on a dataset in TrueNAS Scale (21.04), and when I add a new user with read/write/execute permissions, it seems to get stuck at 50% Reticulating Splines.

Does anybody know why this is, or how to troubleshoot the underlying issue?

Thanks,
Victor

 

[anodos]

Bug waiting for merge of https://github.com/truenas/middleware/pull/6835

 

[victorhooi]

Aha got it - thank you!

Is there any workaround in the meantime, in order to set ACLs on items?

(Also - sorry if naive - but I saw the bug mentions nfs4acl - I actually use SMB - but this is on the dataset itself, and edit permissions - I suppose the "nfs" in the name doesn't mean what I think it does?)

 

[anodos]

Aha got it - thank you!

Is there any workaround in the meantime, in order to set ACLs on items?

(Also - sorry if naive - but I saw the bug mentions nfs4acl - I actually use SMB - but this is on the dataset itself, and edit permissions - I suppose the "nfs" in the name doesn't mean what I think it does?)

You can use getfacl / setfacl from the commandline or set non-recursively from the GUI. NFSv4 vs POSIX1e in this case. If you're used to using more advanced features of ACLs on TrueNAS Core, the POSIX1e ACLs that are currently in SCALE will feel a bit like getting a bowl of soy ice cream when expecting the good stuff.

 

[Ericloewe]

While the Sims reference is amusing, it seems better to me to provide real statuses instead.

 

[anodos]

While the Sims reference is amusing, it seems better to me to provide real statuses instead.

Real status is added in the aforementioned PR. Fix for POSIX1e ACL handling was too close to last freeze/release for Alpha and so it was rolled into the general PR for NFSv4 ACLs.

 

[ornias]

I think it's time to start autoclosing any topic complaining/asking about ACL support by now.
It's what, 2-3 days after the last one that complained/asked? Answers about ACL support are literally ALL-OVER the forums by now >.<

At the moment the previous one asking is LITERALY 4 threads below this one...

 

[anodos]

I think it's time to start autoclosing any topic complaining/asking about ACL support by now.
It's what, 2-3 days after the last one that complained/asked? Answers about ACL support are literally ALL-OVER the forums by now >.<

At the moment the previous one asking is LITERALY 4 threads below this one...

I don't think it's that hard to just keep replying. Auto-closing is rather heavy-handed.

 

[ornias]

@anodos You maybe don't mind it.
Others following the forum for potential issues in SCALE (like me) do mind with garbage following the forum.

Closing for not following the top rule (searching isn't even required, it's literally right there), seems fair.
Topics get closed for less violations of the top rule.

I've answered just this month about 4 times that 21.04 does not include full ACL support.
So anyone still asking is basically completely ignoring the forum rules to get off easy.

 

[beagle]

There should be a PIN with top questions:
(1) ACL is not ready yet
(2) Kurbernetes is not Docker
(3) No, don't migrate your production server without backups from Core to SCALE Alpha ;-)

 

[cyrus104]

Maybe pin major issues at the time, then unpin them once a new fix is released.

 

[ornias]

There should be a PIN with top questions:
(1) ACL is not ready yet
(2) Kurbernetes is not Docker
(3) No, don't migrate your production server without backups from Core to SCALE Alpha ;-)

(4) Automatic migration isn't ready yet
(5) No you can't automatically switch trains from Nightly to Alpha

That would cover about 95% of threads in the past 2 months :')

 

[Ericloewe]

If anybody feels like cleaning that up in a new thread with some detail, ping me and I'll sticky it.