Pyrus mini detected, but transfer error

[mclien]

I'm running debian wheezy with calibre 2.19
My just delivered trekstore Pyrus mini is detected flawlessly ("connected Trekstore").
But when I try to tranfser a book to the device I get an error:

[Errno 17] File exists: '/media/TREKSTOR/Ebooks'

Traceback (most recent call last):
  File "site-packages/calibre/gui2/device.py", line 87, in run
  File "site-packages/calibre/gui2/device.py", line 584, in _upload_books
  File "site-packages/calibre/devices/usbms/driver.py", line 267, in upload_books
  File "site-packages/calibre/devices/usbms/device.py", line 1073, in create_upload_path
  File "os.py", line 157, in makedirs
OSError: [Errno 17] File exists: '/media/TREKSTOR/Ebooks'

Should I delete the Ebooks file on the device before transfering to make it work?

[eschwartz]

Yes, because it appears that the Pyrus Mini uses that location as the root folder for books.

[mclien]

So you say calibre wants to create a file with the name Ebooks, which it can't bacause there is a folder on the Pyrus which is named eBooks??
Does that mean calibre is unable to distinguish upper/lowercase, even tought the OS(GNU/Linux) can??

[itimpi]

Originally Posted by mclien

So you say calibre wants to create a file with the name Ebooks, which it can't bacause there is a folder on the Pyrus which is named eBooks??
Does that mean calibre is unable to distinguish upper/lowercase, even tought the OS(GNU/Linux) can??

Does the Paris by any chance use a FAT based file system for storing books? Only checking because FAT based systems ignore case.

[eschwartz]

Originally Posted by mclien

So you say calibre wants to create a file with the name Ebooks, which it can't bacause there is a folder on the Pyrus which is named eBooks??
Does that mean calibre is unable to distinguish upper/lowercase, even tought the OS(GNU/Linux) can??

It appears that calibre wants to create a folder called "Ebooks" which it cannot do because there is already a file of the same name and case.

Since calibre is performing a bog-standard python os.makedirs call, I would venture to say there is no special secret sauce designed for confusing filenames... though it is possible that as itimpi said, there is a file with a different case but same name, in which case the traditional FAT storage system might throw complaints.

Either way, what is a file called ebooks/Ebooks/eBooks/eBoOKs/anything else doing there in the first place?

[mclien]

@itimpi:
right you are vfat-filesystem on the Pyrus

@eschwartz:
case aside: in the first place the folder* on the divice exists and the in the second place calibre wants to create a file with the name. Whatfor I have no idea. What and if at all folder is then used for books I have no idea, too.

*

ls -l /media/TREKSTOR/
...
-rw-r--r-- 1 foo users  292 Feb 13 19:24 driveinfo.calibre
drwx------ 2 foo users 4096 Feb 12 20:12 eBooks

defenitly folder in the first place.

So if calibre wants the create a folder, then it's complaining it is already there and therfor throws an error. Could it be, that calibre noticed the case diference and then gets stuck becaus ethe filesystem on the device don't?

[kovidgoyal]

That error indicates that your system is mounting the vfat partition with broken options.

The stat() call for /media/TREKSTOR/Ebooks is failling indicating it does not exist, and then the mkdir() call is failing indicating it does exist.

In other words, stat() is case sensitive, but mkdir is not. That is just wrong.

Either delete the folder and let calibre create is for you or rename it to have the case calibre expects. Or better yet fix your system to use the correct mount options for vfat.

EDIT: Just for completeness, it will likely be some mixture of the shortname and iocharset/utf8 mount options. Here are the options from my system for vfat devices. (rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1000 ,fmask=0022,dmask=0077,codepage=437,iocharset=iso8 859-1,shortname=mixed,showexec,utf8,flush,errors=remou nt-ro,uhelper=udisks2)