Bug 5536 - invalid EIO and EPERM when opening files
Summary: invalid EIO and EPERM when opening files
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Local drive redirection (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-19 16:45 CEST by Pierre Ossman
Modified: 2015-05-26 10:23 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2015-05-19 16:45:43 CEST 
Seen on the SLETC Wyse when using a usb stick.

NTFS on the stick:

 cp foo ~/thindrives/usbstorage-0 => EIO
 cp foo ~/thindrives/usbstorage-0 => EPERM
 echo foo > ~/thindrives/usbstorage-0/bar => OK
 echo foo > ~/thindrives/usbstorage-0/bar => EPERM

i.e. the behaviour changes depending on if the target file exists or not.

With FAT on the stick it is only cp that fails, when the target doesn't exist:

 cp foo ~/thindrives/usbstorage-0 => EPERM
 cp foo ~/thindrives/usbstorage-0 => OK

Reminds me a bit of bug 4592.

No problems accessing the files locally on the terminal.
Note You need to log in before you can comment on or make changes to this bug.