NFS Share 'no space available' but nearly empty

[Alex.Bpunkt]

Dear community,

I have created a NFS shared dataset to be used, mainly, for my Jellfin app. Now I ran into that issue that I cannot copy anything on it anylonger as it reports "no space available". Even though only 222Gib of 26TiB are used!

With my limited knowledge I googled a bit and found something about inodes, but not really how to resolve the problem. Also within this community I haven't found what I think I am looking for.

What did I do wrong and how can I fix that? Obviously I would like to use more then only 222Gib of my storage.

Best regards,
Alex

 

[sretalla]

Quotas on that dataset? Does the jellyfin user have write permissions to it?

 

[Alex.Bpunkt]

There are no Quotas set. Jellyfin does have right permissions.
But the problem is not from Jellyfin. I have made the NFS share accessible via my network and loading from my personal PC to this NFS share worked for the first 222gig, but now it says "no space available". Even though I clearly have enough space, theoratically.

 

[Elliot Dierksen]

I think @sretalla is on the right track talking about permissions. I a write fails because it doesn't have permission, the app might interpret that (or report it) as "no space".

 

[Alex.Bpunkt]

As I already said. It is not about Jellyfin. It is from my personal PC where I added the NFS share as network drive. Same from my other devices (windows 10, windows 11, Linux Mint). I am not sure how Jellyfin would prompt this error. As currently I put my stuff via NFS share over as attached network device on it and not via Jellyfin. I am quite certain that Jellyfin has nothing to do with it. As I added the same NFS share (dataset) in Jellyfin and gave it read/write permissions.

I rather guess that I have done something wrong (not intentionally set something) at the creation of the NFS share. I found this Serverfault link which has a very good hint. But due to my limited knowledge I couldnt verify if this is the actual case.
In case this is a valid concern I would seek guidance how to check that on a truenas scale system.

I have my pool where all HDDs are allocated (~26Tib), I created a dataset and made an NFS share out of it. Now it seems that I cannot put more then ~222GiB on it from my Windows and Linux devices (no other OS at hands). Which leads me to the conclusion that not the client (windows, linux) but the server (nfs share from truenas) is the issue.
With no idea how to create a dataset to handle more files.

I am sorry in case I am repetitive or sounding unreasonable, stupid and numb. But I am no linux expert. I have experience in software development but unfortunately far away from operating systems :S

 

[sretalla]

As I already said. It is not about Jellyfin. It is from my personal PC where I added the NFS share as network drive. Same from my other devices (windows 10, windows 11, Linux Mint). I am not sure how Jellyfin would prompt this error. As currently I put my stuff via NFS share over as attached network device on it and not via Jellyfin. I am quite certain that Jellyfin has nothing to do with it. As I added the same NFS share (dataset) in Jellyfin and gave it read/write permissions.

Fine, forget jellyfin.

What permissions do you have on the dataset? And which user are you authenticating as from the PC?

 

[Alex.Bpunkt]

I can check that in detail when I am back at home.
But basically everybody (admin, user, others) has all permissions on this dataset. No login from my network attached devices (PC, Notebook, etc..) required.

Writing the first 222GiB worked fine. Now when I try to copy something it says no space availabe.

 

[sretalla]

No login from my network attached devices (PC, Notebook, etc..) required.

Sounds like maybe guest access is kicking in then... possibly read-only.

 

[Alex.Bpunkt]

But why it should suddenly kick in and work till now (no permissions changed and all set on full access)? Wouldn't be the error message also a different one then "no space available"?