Maximum number of concurrent calls (20) has exceeded with my TrueNAS Scale

TrueNAS General
1

Dear community,

I’m having trouble configuring my TrueNAS Scale

I have 29 share drives to create with several permissions to be given so that users can access the file.

I created 6 share drives without any problem, then I started to configure the 7th drive when the following problem occurred.

In my main dataset I created a child dataset for the SMB share.
I started to create my share drives in this dataset.

So to respect the parent/child tree structure, I have to give access to all my share drives in this dataset and then give access to the other drives.

This implies that the SMB dataset will have several permissions.
I’m up to 20 groups for permissions in this dataset, could this be what’s causing the problem?

2

I had a bit of trouble following, but I think I got the gist of it.

They identified a something similar sounding issue here:
https://ixsystems.atlassian.net/browse/NAS-129869

Which version of SCALE are you on?

Edit: Actually, when I read the related issues I see that the planned fix version is Fangtooth 25.04.

3

I’m using the 24.10.0.2 version

4

There’s a UI limitation in how its making backend API calls to resolve IDs to UID/GIDs that causes problems if user has more than 20 ACL entries.

The backend was changed to allow consumers to set entries by name in 25.04, but the change was too large to backport to 24.10.

This can be worked around by using the API to set the ACL in 24.10… or maybe trying to get by with fewer entries in the ACL. We support up to 1024 entries for the NFSv4 acltype.

5

Thanks for the information

What exactly should I look for in the API doc section to be able to fix my problem?

6

You call look at sample of core.get_jobs | jq output for when you’ve successfully set an ACL to see a representative payload, then call filesystem.setacl endpoint with a similar payload but with more groups.

1 Like