Copy/Move permissions issue with build 3889

[foonji]

Hi all,

I'm currently using Photo Mechanic 6 Build 3889 on Windows 10.

Since this latest build I've been unable to use the copy/move tool as I usually do to relocate local images to my NAS server.

It has been throwing this error back at me:
"Unable to update XMP sidecar file at 'Z:\backup\Photo Library\2019\10\19 - Family\.tmp_000042300000000e.xmp', file may not be writeable."

It goes through and creates the folder structure "\2019\10\19 - Family\", obviously some of it already exists such as the year, but appears that when it comes to the file transfer part is where it fails and errors. Once this happens if I am doing a 'move' rather than 'copy' the first attempted file to move is lost. It never ends up in the destination folder, and it is removed from the source folder.

Nothing has changed on my server, the permissions are fine for the user, I can read and write files with no problems through the smb share with windows explorer.

[Kirk Baker]

Hi all,

I'm currently using Photo Mechanic 6 Build 3889 on Windows 10.

Since this latest build I've been unable to use the copy/move tool as I usually do to relocate local images to my NAS server.

It has been throwing this error back at me:
"Unable to update XMP sidecar file at 'Z:\backup\Photo Library\2019\10\19 - Family\.tmp_000042300000000e.xmp', file may not be writeable."

It goes through and creates the folder structure "\2019\10\19 - Family\", obviously some of it already exists such as the year, but appears that when it comes to the file transfer part is where it fails and errors. Once this happens if I am doing a 'move' rather than 'copy' the first attempted file to move is lost. It never ends up in the destination folder, and it is removed from the source folder.

Nothing has changed on my server, the permissions are fine for the user, I can read and write files with no problems through the smb share with windows explorer.

If you uninstall build 3889 and go back to build 3558 (http://forums.camerabits.com/index.php?topic=12699.0) does the problem go away?

-Kirk

[foonji]

Hi Kirk, correct, this issue does not occur in 3558.

and on a side note, this issue does not occur either > http://forums.camerabits.com/index.php?topic=12892.msg63670#msg63670

[Kirk Baker]

Please update to the latest build of PM6: http://forums.camerabits.com/index.php?topic=12940.0

Thanks,

-Kirk

[foonji]

Thanks Kirk - However it still occurs in 3954

[Kirk Baker]

Thanks Kirk - However it still occurs in 3954

OK, tell me more about what's going on.  What are the permissions of the folder that PM6 is creating yet it can't put files there?

-Kirk

[foonji]

This is the permissions on the server (user/group changed for security);

Folder created by Photo Mechanic:

Code: [Select]

drwxrwx---+ 2 user1  group1  uarch 6 Nov 15 07:53 13 - Arlo
Existing folder created by Photo Mechanic in August prior to this issue:

Code: [Select]

drwxrwx---+ 10 user1  group1  uarch   10 Aug 8 16:57 06

Now looking into it a bit closer the temp hidden files (images and xmp) created by Photo Mechanic also exist in the folder. So I guess the error occurring on the renaming of those.

Code: [Select]

-rwxrwx---+ 1 user1  group1  uarch 59595693 Oct 13 16:29 .tmp_0000129400000001.nef
-rwxrwx---+ 1 user1  group1  uarch 3009 Oct 13 17:52 .tmp_0000129400000001.xmp


[Kirk Baker]

Now looking into it a bit closer the temp hidden files (images and xmp) created by Photo Mechanic also exist in the folder. So I guess the error occurring on the renaming of those.

Code: [Select]

-rwxrwx---+ 1 user1  group1  uarch 59595693 Oct 13 16:29 .tmp_0000129400000001.nef
-rwxrwx---+ 1 user1  group1  uarch 3009 Oct 13 17:52 .tmp_0000129400000001.xmp


Are you able to rename those files from the command prompt?

-Kirk

[foonji]

No problems renaming the files from both the command prompt and windows through the smb share.

[foonji]

Any progression with this?

[Kirk Baker]

Any progression with this?

No.  We are unable to reproduce with our own SMB shares.

-Kirk

[foonji]

Oh ok, guess I'll rollback to 3558 and stay with that then since it's working without a drama.