I have recently upgraded from TrueNAS Core to TrueNAS Scale Dragonfish-24.04.2.3. Since then I have had occasional difficulties opening Office files (so far *.docx and *.xlsx) on network drives made available via SMB.
The problem does not affect all Office files and I cannot yet recognize a pattern. That’s why I’m posting here what I know so far and would be grateful for any tips:
Office files cannot be opened on the Windows client. Excel/Word shows: '[filename] could not be opened'.
In the properties of the file under Windows there is no meta information under Details (apart from the creation date). Under Security it says: The requested security information is not available or cannot be displayed.
The log file log.smbd then contains the following entry, for example:
[2024/11/04 12:00:10.901506, 0] ../../source3/smbd/open.c:3467(smbd_calculate_maximum_allowed_access_fsp)
smbd_calculate_maximum_allowed_access_fsp: Could not get acl on file path/to/file.xlsx: NT_STATUS_INTEGER_OVERFLOW
This entry often appears in the log file log.winbindd: ../../source3/winbindd/winbindd_getpwnam.c:142(winbindd_getpwnam_recv) Could not convert sid S-0-0: NT_STATUS_NONE_MAPPED
If I copy the file via SSH to my computer and from there to the network drive, everything works. The file itself is not broken.
If the file is renamed, copied or similar via Windows Explorer, the message appears:
You cannot copy the file due to an unexpected error. If the error is still displayed, you can search for this problem using the error code in the help.
Error Ox8W70216: Arithmetic result exceeds 32 bits.
Does anyone have an idea or a hint how I can solve this? Or where to look for more detailed logs?
FWIW, I had a similar issue due to files including non-NTFS characters and my CORE dataset having had the Apple Charset Compatibility (ACC) checkbox checked because I run a Mac household.
Somehow ACC got turned off in the transition to SCALE due to the SMB share preset changing for every SMB dataset that was not a Time Machine dataset. In my case it was presets changing from ‘no preset’ in CORE to ‘default’ in SCALE, which disables ACC, I guess?
So if you had ACC turned on in the past, double-check if it still is. You’d find it under the SMB Share settings for each share by selecting “advanced settings”. If you didn’t have ACC turned on in the past, then it’ll be a different issue. Good luck.
You saw getacl failing with NT_STATUS_INTEGER_OVERFLOW? If not, then you didn’t see this issue. Telling users to make arbitrary configuration changes will make it harder for everyone to track down the issue.
Similar issue on 24.10.0.1. I upgraded CORE last week and problem started on Scale. If I download the file with scp no problem experienced. Bigger excel files have problem.
edit: after downgrade to 24.10 problem is resolved.
I’m also experiencing issues with SMB after the upgrade to 24.10.0.1.
I got an unexpected network error every time I tried copying a file from my NAS to my windows machines and my TrueNAS system reported the following error…
Core files for executables have been found in /var/db/system/cores/.Please open the shell, copy any core files present in /var/db/system/cores/ and then generate a system debug. Next, create a ticket at https://ixsystems.atlassian.net/ and attach the core files and debug. After creating the ticket, the core files can be removed from the system by opening shell and entering 'rm /var/db/system/cores/*'.
I reverted to my 24.10.0 boot environment and the issue went away.
I have the .zst files but I don’t know how to read them
To summarize this issue: there’s a limit on maximum number of ACEs in ACL in SMB in SCALE that is lower than it was in Core. STATUS_INTEGER_OVERFLOW is an unfortunate translation for ERANGE. This will be fixed in 24.10.1 via NAS-132344.
