core->scale migration: SMB behaviour change: hide unreadable
Description
Problem/Justification
Impact
Activity

Metis IT June 5, 2023 at 12:43 PM
so i was correct in noticing a behavioral change after the migration? currently we can live well with “hide unreadable = yes”.
just to clarify, without this setting, now you can see the existance of files even when you have 0 rights based on the ACL of that file.
did you perform performance tests regarding the impact of the parameter? our metadata cache hit ratio is close to 100% so at least it should only result in a CPU impact.

Andrew Walker June 2, 2023 at 9:11 PM
This would add an additional permissions check in VFS where linux kernel has none and would be too large of an impact to metadata ops perf.

Automation for Jira June 2, 2023 at 8:18 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Details
Details
Assignee

Reporter

after migrating from Core 13.0U4 to Scale 22.12.2 the user experience on SMB shares changed: we had ACL on folders inside a shared dataset configured based on group membership so that folders are only visible and accessible to certain users. in Core, if they had no rights, they did not see them, in Scale that had changed (seeing 100 more inaccessible foldera can be quite confusing…).
workaround: global custom paramter:
hide unreadable = yes
btw: maybe that's worth a service or share checkbox settting?