Quote:
Originally Posted by BetterRed
I had them on a standard windows/ntfs rig, on a fixed internal drive. I also had a problem with hundreds of them turning up in the recycle bin
Both problems were repeatable but neither caused any loss of data or library corruption - Check Library saw them as extra author folders - but I first noticed them in my backup logs.
Both problems were fixed
|
Well, the problem
as Kovid explained it was:
Quote:
For some reason, your OS is raising permission denied (EPERM) errors
when calibre tries to delete a non-empty directory, instead of
ENOTEMPTY, which is causing the problem. Do you have your calibre
library on some kind of special filesystem?
|
and
Quote:
In any case, I have changed the code to not rely on the OS sending the
proper error code, it will now manually check if the directory is empty.
That should fix your problem.
|
Whatever the problem was, that is what caused it for me.
And I got them in the parent directory to my library folder (in "Calibre Libraries") -- also no loss of data, just a pain in the neck to clean up after. Either way, it shouldn't cause errors until after the book was copied, so...
Quote:
|
I have a vague memory that the file name truncation length changed from from 36 to 34 or something like that - it seemed to disturb a few people - although I can't recall whether they were of a material or aesthetic kind.
|
Aesthetic, definitely. The change was deliberate and calibre still does it.
