Cannot Copy Files - "Out of Space" Even with several TB free

TrueNAS General
, ,
1

I am trying to copy about 256gb of data into my dataset. At first it was within the NAS itself, but I then moved it to an external SSD. Trying to copy it back up, I still get the same error that I need another 69gb free to move the data. However, I still have about 13tb free. I did check for quotas and there is no set quota for my user. Looking at dataset details I have 20.92TiB available to the dataset. Any ideas on how to fix? System info below. The smb share is mounted on my windows 11 machine. I tried in my arch linux laptop as well.

NAME        SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
Apps        928G  17.0G   911G        -         -     0%     1%  1.00x    ONLINE  /mnt
Media      43.7T  12.0T  31.6T        -         -     0%    27%  1.00x    ONLINE  /mnt
boot-pool   460G  4.95G   455G        -         -     0%     1%  1.00x    ONLINE  -

Dragonfish-24.04.2
RaidZ2 6 wide, 8TB discs
8TB used 20TB Free
i5-14500
32GB Ram
Mirrored SSDs

2

Suggest you provide full system details (HW & SW version) and screenshots of error messages and status.

Details on the client and process being used would also be useful.

3

Updated OP with more detail.

4

Can you capture the error message as well… is it on the client or the system?

5

It was on the client. I disconnected the smb share from the client and re-added it and it seemed to work, even though i believe i did that before as well.

6

Thanks for update and glad its fixed.
Its not clear whether it was a temporary client of NAS issue…obviously, we’d like to fix any NAS issues.

7

I do frequently have an issue where if I have 2 shares mounted with the same user, I get an error along the lines of “I can’t have 2 shares mounted under the same user”. Is that because they are part of the same dataset?

8

I don’t know of a restriction like that.

With most issues, we find resolutions if you provide all the details. It might be a client issue or a NAS configuration issue, but without details, we’re all just guessing.