[Borgbackup] Backup error read: [Errno 5] Input/output error on CIFS mount

[Jörn Körner]

Am 03.01.2018 um 11:06 schrieb Thomas Waldmann:
> On 01/03/2018 10:32 AM, Jörn Körner wrote:
>>> The option "ro" means read only. Have you tried without it?
>
> To look at this, I am missing some info.
>
> If you have a github account, you could also file this as an issue on
> our github issue tracker:
>
> - your borg version and how you obtained/installed it, your python
> version (if relevant)
> - your OS / version (on the machine doing the mount)
> - your OS / version (on the machine providing the smb share you mount)
I dont' know if it's a bug or just an user error (me)
If it turns out that's a but I'll create a new issue.


> Does it only say "Backup error read: [Errno 5] Input/Output error
> <path>" or is there more info, like a python traceback?
There's no python traceback, just an borg-error like

> Can you reproduce the error?
Yes, kind of. Details follow

>
> Can you run an strace and post the relevant part of it?
>
>> Anyway when mounting rw it seems to work. Does borg tries to
>> access/update atime?
> Access: sure (atime comes as part of stat() result which is also needed
> for other reasons).
>
> Update: borg tries to open files in a mode that does not update atime,
> but this mode is only available under specific circumstances (like when
> running as root or owning the file). If the mode is not available, it
> accesses the files normally, which usually leads to an atime update done
> by the filesystem / OS itself (at least when mounted rw).
>
>> It shows out that adding '--noatime' to 'borg create' does resolve this
>> behaviour.
> That's interesting.
>
> I can look up what's happening as soon as I know your precise borg version.
>

I'll collect all information and also a way to reproduce in my next reply.