[victorhooi]

I have jDownloader installed on my macOS machine.

I've saving files to a network file share (TrueNAS Scale), which is mounted on the macOS machine via SMB.

Previously, this was working fine.

All of a sudden however, jDownloader won't download files, and has the error message:

> Skipped - Disk is full

However, this doesn't really make sense - as the network file share has plenty of space (about 48 TB free). The particular share it's saving to has consumed about 4 TB so far (not sure if that number is significant).

root@truenas[~]# zfs list
NAME                                                              USED  AVAIL     REFER  MOUNTPOINT
boot-pool                                                        5.25G  13.2G       96K  none
boot-pool/ROOT                                                   5.24G  13.2G       96K  none
boot-pool/ROOT/22.02.0.1                                         2.62G  13.2G     2.61G  legacy
boot-pool/ROOT/22.02.1                                           2.62G  13.2G     2.62G  legacy
boot-pool/ROOT/Initial-Install                                      8K  13.2G     2.61G  /
boot-pool/grub                                                   8.17M  13.2G     8.17M  legacy
foobar-nas                                                       4.17T  48.0T      166K  /mnt/foobar-nas

I've also tested copying files just now (around 5GB) to the network share via Finder (file manager) in macOS - and this worked fine.

Can you think of any reason why jDownloader is suddenly refusing to write to the network file share?

Or any way to dig deeper into the issue?

Thanks!

[Jiaz]

@victorhooi: please check complete path and pay attention to case sensitivity. No changes from our side so either the path has changed OR the available disk space is not reported correctly to application
Please provide a log, see https://support.jdownloader.org/Know...d-session-logs and post logID here, then we can check it
so my ideas/guesses are:
1.) changed/wrong path
2.) permissions/ownership issues
3.) maybe the mountpoint not correctly reporting the available disk space?
with a log I should be able to tell you more

[victorhooi]

Closing the loop on this - this appeared to be a permissions issue - I did a recursive chmod from the root again, just in case, and jDownloader works now =).

Curious - is there any way for jDownloader to differentiate (assuming SMB) whether it's actually a diskfull situation, or whether it simply doesn't have the ACLs to write?

[Jiaz]

@victorhooi: Thanks for the feedback!
I need a log for this, see https://support.jdownloader.org/Know...d-session-logs but with SMB involved, could be that missing permissions also mean that missing permission to check required disk space.
A log may contain hints why JDownloader reports *full disk* instead of *wrong folder*.
Either you can recreate the issue again by breaking your permissions or maybe you still have logs from that error and create/upload log from that session/time window