Smb/cifs mount permission issue.

[deajan]

Smb/cifs mount permission issue.

[deajan]

I'm not sure if this is and osync bug or something between your configuration and rsync, and the logs won't be sufficient here.

Have you tried to set times and permissions on the files manually as the user running osync ?
If you cannot find the issue, can i get temporary access to that server to have some tests ?

[dcmwai]

I think that you cannot change the permission or xattr on that drive.
Can we somehow ignore the permission and also xattr?

I've partial debug log here.
https://gist.github.com/dcmwai/fe41361ccbb7ca783c49

not sure if that is helpful...

[deajan]

Your last gist showed that you already disabled ACL and XATTR copy in configs.
But you MUST have the rights to change at least timestamps, which it seems you don't have either.
You must find where your problem lies, this isn't osync related think.

Have you tried to test changing perms as root ? If yes, grant your current user more rights on the folder / share via samba.
I think I've read your samba share is on ZFS, have you set xattr=sa ?

[dcmwai]

This is more complicated than I though...

This is related to:
owner
group
permission
dir time

local (ocfs2) ---> Remote (smb)
Limitation:
Smb don't take owner, group and permission
(Root)So when copy from local to remote, we cannot have owner group and permission set
--no-perms --no-owner --no-group
(User) don't have permission to change directory time
--omit-dir-times

local (ocfs2) <--- Remote (smb)
Limitation:
(Root)So when copy from local to remote, we need to have owner group and permission set
Without owner group and permission the files will belong to root and no on will be able to read it...

(User) don't have permission to change directory time
--omit-dir-times

I think we might have to define extra permission according to slave type...
Which is going complicated...

[dcmwai]

I've make an ugly patch.
I don't like it much.

I think you have a better way to do it.

[deajan]

Usually smb allows setting owner, perms and timestamps, especially if you told me it works as root.
You should maybe check your permissions in smb.conf for that user.

Not using timestamps is a major drawback because rsync relies on timestamps to know which file is newer, this is definitly not the good way of doing.

[deajan]

While it's not the best solution, why don't you run osync with sudo privileges, or even as root ?
See the documentation http://netpower.fr/projects/osync/osync_0.99RC4.html#toc-Subsection-2.3 , you may run osync as a standard user and allow this user to sudo certain commands like rsync.
This way, osync is basically run as your sync user but rsync has full root privleges.

[dcmwai]

Let me think again.
I need check where the limitation is...
When doing smb mount, there are some limit...

[deajan]

Any updates ?
Btw, is there a way to get an RW access to that wiki so i can update some details ?

[dcmwai]

I switch that to dfs without sync...
I think there are some strange factor here..

1. I'm runnig the script as users and cause changing the directory creation time error (users in linux cannot change time unless it is sudo)
2. Because I mount the cifs as user A, the nas don't allow this user A sync or add other users access in the files/folder...

Under the above 2 restriction... (I think...)
we have to run it as root and a cifs users which have the access to change the cifs ACL.
But that it come another problem... The NAS and linux server don't have same uid/gid (because of how the nas handle it UID/GID) so that why I drop this idea and go to dfs...

Thank you for the help

P.s I still think it is good to have ignore users and group permission on the script.
But it is missing a feature on if running the osync as root, who files it should be after sync to local...

Thank again.

[deajan]

Well, thank you for your explanation.
There are things i don't understand like why do you sync to a NAS ?

Also, why don't you use osync the way it's designed, sync over ssh instead of over smb ?

Anyway, wish you good luck with your case.

As for the user / group permissions, not syncing them would be a great drawback for a sync software. What's your point ? If you cannot sync permissions, you cannot sync time changes which is needed for sync software.