Hi,
Which file system are you using on DataDiskA?
Could it be that it’s e.g. FAT32 and you’re hitting the 4GB file size limit?
Or do you have lots of small files and (on a Linux filesystem) you’re running
out of inodes? (you can check with “df -i”)
Or maybe there’s a quota on the disk? (but depending on circumstances, this
would result in a different error message)
Anyway, it’s an error from the system I/O, nothing that gPodder creates on its
own.
Hope this helps,
Thomas
On 29.08.2020, at 09:32, Michael Stanich <michael.r.stanich@xxxxxxxxx> wrote:
Hello,
I'm experiencing some difficulty with gPodder 3.10.16(2020-06-21).
System: I'm running Linux Mint 19.1, and switched to the flatpak from the
package manager version
The reason for upgrading was that a new podcast which was recommended to me
wouldn't download, giving 404 errors despite being accessible via browser
using the link in the RSS feed. I assumed it may be due to the old version I
was using and updated to 3.10.16 by installing the flatpak. That podcast now
shows as having the episodes downloaded but only has files ending ".partial"
in the download location. Since some new episodes for other podcasts have
downloaded correctly, I'm thinking this might be a gPodder issue.
The other issue I'm having with the new version is that when trying to
download new episodes it started giving the message "Failed: I/O Error: No
space left on device: None - <podcast name>". I don't understand how this
could be, the drive has free space. I did review FAQ and the archives of the
mailing list, and figured I'd reach out here before considering this a bug.
I found the email chain with subject "[gpodder-devel] iPodTouch always
'full'" which seems like it might be a similar issue. My issue is slightly
different, I'm doing the initial download of episodes and I'm using
/DataDiskA/Podcasts as the environment variable for storage location. This
location was previously successful with the old version of gPodder(I don't
recall but it was likely 3.1 or earlier) and with about 100 assorted new
episodes before this error started showing up. I verified that I can add
things to or remove them from the destination hard drive, and have set 775 as
the permission for that area so I'd expect that it's not a permission issue.
I saw the request for the output of df -h in the email chain so here it is:
df: /run/user/1000/doc: Operation not permitted
Filesystem Size Used Avail Use% Mounted on
udev 5.6G 0 5.6G 0% /dev
tmpfs 1.2G 1.6M 1.2G 1% /run
/dev/sda1 110G 47G 58G 45% /
tmpfs 5.7G 292M 5.4G 6% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 5.7G 0 5.7G 0% /sys/fs/cgroup
/dev/sdb1 900G 300G 555G 36% /DataDiskA
/dev/sdd 459G 45G 391G 11% /DataDiskC
/dev/sdc1 459G 122G 314G 28% /DataDiskB
tmpfs 1.2G 76K 1.2G 1% /run/user/1000
/dev/sdj1 2.8T 2.6T 142G 95% /media/mstanich/TOSHIBA EXT
/dev/sdi1 1.9T 1.3T 597G 68% /media/mstanich/FreeAgent GoFlex Drive
As you can see, /DataDiskA has plenty of space, so I can't explain why it's
saying it's out of space. I'd appreciate any suggestions or let me know if I
should file a bug report.
Sincerely,
Mike
