Permission denied on accessible file

Asked by Vincent Bastos ( Lava Lab Software )

Duplicity is throwing the following error on 7 files which are accessible. These files are in a mount partition which has the same permissions.

Error [Errno 13] Permission denied: '/mnt/texalliance/DPT PRODUCTION/COMMANDES PAR CLIENT/GEMO/HIVER 2011/11W10030 CIAMILLE - ZEJIANG 2000 PCS FEMME.xls' getting delta for DPT PRODUCTION/COMMANDES PAR CLIENT/GEMO/HIVER 2011/11W10030 CIAMILLE - ZEJIANG 2000 PCS FEMME.xls

What other reason could give this error?

Question information

Language:
English Edit question
Status:
Answered
For:
Duplicity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Kenneth Loafman (kenneth-loafman) said :
#1

It's possible the file is open in write mode on the remote FS. On Windows,
that's an exclusive open, no read allowed.

...Ken

On Wed, Mar 2, 2011 at 11:40 PM, Vincent Bastos <
<email address hidden>> wrote:

> New question #147631 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/147631
>
> Duplicity is throwing the following error on 7 files which are accessible.
> These files are in a mount partition which has the same permissions.
>
> Error [Errno 13] Permission denied: '/mnt/texalliance/DPT
> PRODUCTION/COMMANDES PAR CLIENT/GEMO/HIVER 2011/11W10030 CIAMILLE - ZEJIANG
> 2000 PCS FEMME.xls' getting delta for DPT PRODUCTION/COMMANDES PAR
> CLIENT/GEMO/HIVER 2011/11W10030 CIAMILLE - ZEJIANG 2000 PCS FEMME.xls
>
> What other reason could give this error?
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
Vincent Bastos ( Lava Lab Software ) (vincentbastos) said :
#2

I think that the file was never properly closed by the Windows machine because all the user workstations were shutdown.

Revision history for this message
edso (ed.so) said :
#3

you can verify this by running process explorer of microsoft sysinternals on the windows server and find the open handle. just fyi.

ede/duply.net

Can you help with this problem?

Provide an answer of your own, or ask Vincent Bastos ( Lava Lab Software ) for more information if necessary.

To post a message you must log in.