Weird no free space error

[Jedi]

Hello, I am trying to add an ebook from calibre to my Libra 2 device using OPDS Catalog and I get the following message.

"Could not save file to...No space left on device"

I also tried to change the default folder from SD to root, didn't helped. This is not the first time I am using this method to transfer files, didn't had problems in the past.

The file is an .epub approximately 15mb. I have 60gb+ free storage.

Thank you

[hius07]

This is not the message from KOReader but from the system.
Anyways, crash.log would be helpful.
Turn on Tools - More tools - Developer options - Enable debug logging (menu is accessible in file browser mode only).

[JSWolf]

Originally Posted by Jedi

Hello, I am trying to add an ebook from calibre to my Libra 2 device using OPDS Catalog and I get the following message.

"Could not save file to...No space left on device"

I also tried to change the default folder from SD to root, didn't helped. This is not the first time I am using this method to transfer files, didn't had problems in the past.

The file is an .epub approximately 15mb. I have 60gb+ free storage.

Thank you

It could be that because the filesystem is Fat32, that you've run out of directory entries. Try creating another directory and moving some of the files to this new directory and see how the download goes.

[Jedi]

Originally Posted by JSWolf

It could be that because the filesystem is Fat32, that you've run out of directory entries. Try creating another directory and moving some of the files to this new directory and see how the download goes.

Worked, I changed to onboard folder instead of SD and downloaded the file.
I suppose I can't do much about fixing this problem?

Thank you.

[Frenzie]

It seems unlikely that you'd have reached a file limit since that means many thousands of files and folders, but in any case it's a per folder limit, so simply moving a few thousand into a subfolder should resolve the problem if JSWolf's hunch is correct.

[Jedi]

Originally Posted by Frenzie

It seems unlikely that you'd have reached a file limit since that means many thousands of files and folders, but in any case it's a per folder limit, so simply moving a few thousand into a subfolder should resolve the problem if JSWolf's hunch is correct.

That's interesting, I suppose those folders are system folders or koreader files/ folders? Because the only thing I've transfered to my device are 20 books with overall 30-40mb size.

I am afraid to move something and make my reader crashing
Sorry, don't have a clue about those things.

When I installed the koreader for me it was like winning the marathon

[JSWolf]

Originally Posted by Frenzie

It seems unlikely that you'd have reached a file limit since that means many thousands of files and folders, but in any case it's a per folder limit, so simply moving a few thousand into a subfolder should resolve the problem if JSWolf's hunch is correct.

https://stackoverflow.com/questions/...irectory-limit

The maximum number of files within a directory of a FAT file system is 65,536 if all files have short filenames (8.3 format). Short filenames are stored in a single 32-byte entry.

That means the maximum size of a direcotry (file) is 65,536 * 32 bytes, i.e. 2,097,152 bytes.

Short filenames in 8.3 format consists of 8 characters plus optional a "." followed by maximum 3 characters. The character set is limited. Short filenames that contain lower case letters are additionally stored in a Long File Name entry.

If the filename is longer (Long File Name), it is spread over multiple 32-byte long entries. Each entry contains 13 characters of the filename. If the length of the filename is not a multiple of 13, the last entry is padded.

Additionally there is one short file name entry for each Long File Name entry.

2 32-byte entries are already taken by the "." and ".." entries in each directory (except root).

1 32-byte entry is taken as end marker?

So the actual maximum number of files in a directory depends on the length of the filenames.