[Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)

[just subscribed for rsync-qa from bugzilla via rsync]

https://bugzilla.samba.org/show_bug.cgi?id=11414

--- Comment #7 from Michal Ruprich  ---
Thank you Kevin. This makes sense.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)

[just subscribed for rsync-qa from bugzilla via rsync]

https://bugzilla.samba.org/show_bug.cgi?id=11414

--- Comment #6 from Kevin Korb  ---
There was a change made in 3.1.0...

- Added a way for more than one group to be specified in the daemon's
  config file, including a way to specify that you want all of the
  specified user's groups without having to name them.  Also changed the
  daemon to complain about an inability to set explicitly-specified uid/gid
  values, even when not run by a super-user.

So, even if a user is in more than one group once you set the gid option the
listed groups are all that user gets to be in now.

I am not sure if the lack of permission setting is a bug or an rsyncd feature
and I don't know if it is still the case in the current version.  I don't
really feel like setting up a test case to find out.  IMO if you are running
rsyncd without read only = yes and/or withe authentication you are mis-using
rsyncd.  If you want these things use rsync over ssh where you have decent
authentication+security.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)

[just subscribed for rsync-qa from bugzilla via rsync]

https://bugzilla.samba.org/show_bug.cgi?id=11414

--- Comment #5 from Michal Ruprich  ---
There is one more thing that doesn't make sense to me. Even if the operation of
changing the group fails, why doesn't rsync finish other things under the -a
option. For instance the permissions of the original file are 0644 and if the
chgrp error occurs, the destination permissions are just 0600. The user tester
owns the destination file and it should be able to change the permissions.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)

[just subscribed for rsync-qa from bugzilla via rsync]

https://bugzilla.samba.org/show_bug.cgi?id=11414

--- Comment #4 from Michal Ruprich  ---
I see. I never looked at the ps aux output during the transfer so all I saw was
the user that launched the daemon. So I assume that the chgrp error that occurs
without the fake super option is the correct behaviour and the previous version
did this wrong?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)

[just subscribed for rsync-qa from bugzilla via rsync]

https://bugzilla.samba.org/show_bug.cgi?id=11414

--- Comment #3 from Kevin Korb  ---
Oops, I replied to this on the email list instead of the bugzilla.  Sorry for
the extra noise...

It isn't running as root (it probably never should).  It is launched as
root.  It is running as tester:tester just like you set it to.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: [Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)

[Kevin Korb via rsync]

It isn't running as root (it probably never should).  It is launched as
root.  It is running as tester:tester just like you set it to.

On 11/06/2017 10:31 AM, just subscribed for rsync-qa from bugzilla via
rsync wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=11414
> 
> --- Comment #2 from Michal Ruprich <mrupr...@redhat.com> ---
> I stumbled upon this bug and I have a question. I get the chgrp error even 
> when
> running the daemon as root. 
> 
> #ps -aux | grep rsync
> root 18486  0.0  0.0 114696   568 ?Ss   09:41   0:00 rsync 
> --daemon
> 
> I have configured a module in /etc/rsyncd.conf like this:
> [my_data]
> comment = test dir for rsync
> path = /home/tester
> read only = no
> uid = tester
> gid = tester
> 
> Now when I try to copy file 'data' to this module:
> # rsync -av data localhost::my_data
> sending incremental file list
> data
> rsync: chgrp "/.data.CFttwz" (in my_data) failed: Operation not permitted (1)
> 
> sent 86 bytes  received 117 bytes  406.00 bytes/sec
> total size is 0  speedup is 0.00
> rsync error: some files/attrs were not transferred (see previous errors) (code
> 23) at main.c(1178) [sender=3.1.2]
> 
> This doesn't happen with version 3.0.9. And I think that this should not
> happen. It works fine with the 'fake super' option set to 'yes' but the daemon
> runs under root and the fake super option says: "This allows the full
> attributes of a file to be stored without having to have the daemon actually
> running as root." From this description I would assume that you don't need the
> 'fake super' option to transfer all attributes when the daemon runs under root
> right?
> 

-- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
Kevin Korb  Phone:(407) 252-6853
Systems Administrator   Internet:
FutureQuest, Inc.   ke...@futurequest.net  (work)
Orlando, Floridak...@sanitarium.net (personal)
Web page:   http://www.sanitarium.net/
PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,



signature.asc
Description: OpenPGP digital signature
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)

[just subscribed for rsync-qa from bugzilla via rsync]

https://bugzilla.samba.org/show_bug.cgi?id=11414

--- Comment #2 from Michal Ruprich <mrupr...@redhat.com> ---
I stumbled upon this bug and I have a question. I get the chgrp error even when
running the daemon as root. 

#ps -aux | grep rsync
root 18486  0.0  0.0 114696   568 ?Ss   09:41   0:00 rsync --daemon

I have configured a module in /etc/rsyncd.conf like this:
[my_data]
comment = test dir for rsync
path = /home/tester
read only = no
uid = tester
gid = tester

Now when I try to copy file 'data' to this module:
# rsync -av data localhost::my_data
sending incremental file list
data
rsync: chgrp "/.data.CFttwz" (in my_data) failed: Operation not permitted (1)

sent 86 bytes  received 117 bytes  406.00 bytes/sec
total size is 0  speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1178) [sender=3.1.2]

This doesn't happen with version 3.0.9. And I think that this should not
happen. It works fine with the 'fake super' option set to 'yes' but the daemon
runs under root and the fake super option says: "This allows the full
attributes of a file to be stored without having to have the daemon actually
running as root." From this description I would assume that you don't need the
'fake super' option to transfer all attributes when the daemon runs under root
right?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Bug 11414] rsync: chgrp /.filename.5afK5X (in dirdir) failed: Operation not permitted (1)

[samba-bugs]

https://bugzilla.samba.org/show_bug.cgi?id=11414

Nguyen Si Nhan nhanngu...@0937686468.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Nguyen Si Nhan nhanngu...@0937686468.com ---
When I add this line to rsyncd.conf it's ok:
fake super = yes

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[Bug 11414] New: rsync: chgrp /.filename.5afK5X (in dirdir) failed: Operation not permitted (1)

[samba-bugs]

https://bugzilla.samba.org/show_bug.cgi?id=11414

Bug ID: 11414
   Summary: rsync: chgrp /.filename.5afK5X (in dirdir) failed:
Operation not permitted (1)
   Product: rsync
   Version: 3.1.1
  Hardware: x64
OS: Linux
Status: NEW
  Severity: normal
  Priority: P5
 Component: core
  Assignee: way...@samba.org
  Reporter: nhanngu...@0937686468.com
QA Contact: rsync...@samba.org

Notice : With The configuration file below in version 3.0.6,it is working . 
-


-My rsync's config (rsyncd.conf):
==
lock file = /var/run/rsync.lock
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
ignore errors= true
uid = sfftp
gid = sfftp
reverse lookup = no
[9tlocal]
path=/sfarm/9tlocal/
uid = www
gid = www
auth users = 9tlocal
secrets file = /etc/rsyncd.secrets
read only = no
log file = /var/log/rsyncd9tlocal.log


However I got a problem with rsync daemon on version 3.1.1:

When I execute this cmd :
rsync -avz --progress --delete /data/client/ 9tlocal@10.76.0.195::9tlocal

It sync data to dir /sfarm/9tlocal/ but It show these error log:
rsync -avz --progress --delete /data/client/ 9tlocal@10.76.0.195::9tlocal
Password: 
sending incremental file list
rsync: chgrp /. (in 9tlocal) failed: Operation not permitted (1)
rsync: failed to open /syn_pre_update.log (in 9tlocal), continuing:
Permission denied (13)
rsync: failed to open /test (in 9tlocal), continuing: Permission denied (13)
./
syn_pre_update.log
  2,017 100%0.00kB/s0:00:00 (xfr#1, to-chk=1/3)
test
  1,073,741,824 100%   63.80MB/s0:00:16 (xfr#2, to-chk=0/3)
rsync: chgrp /.syn_pre_update.log.4kTDrH (in 9tlocal) failed: Operation not
permitted (1)
rsync: chgrp /.test.yVQDby (in 9tlocal) failed: Operation not permitted (1)

sent 1,044,817 bytes  received 486 bytes  27,874.75 bytes/sec
total size is 1,073,743,841  speedup is 1,027.21
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1165) [sender=3.1.1]

ls -al /data/client/
total 1048592
drwxr-xr-x 2 root root   4096 Th07 27 14:07 .
drwxr-xr-x 3 root root   4096 Th07 27 11:17 ..
-rw-r--r-- 1 root root   2017 Th07 27 14:07 syn_pre_update.log
-rw-r--r-- 1 root root 1073741824 Th07 24 14:34 test



ls -al /sfarm/9tlocal/
total 1048592
drwxr-xr-x 2 www www4096 Th07 27 14:07 .
drwxr-xr-x 5 rootroot   4096 Th07 27 11:25 ..
-rw--- 1 www www2017 Th07 27 14:58 syn_pre_update.log
-rw--- 1 www www  1073741824 Th07 27 14:58 test


===
Finally I re-run cmd with below option(replace option -a by -r )it's OK : 

rsync -rvz --progress --delete /data/client/ 9tlocal@10.76.0.195::9tlocal

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

DO NOT REPLY [Bug 5939] rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1)

[samba-bugs]

https://bugzilla.samba.org/show_bug.cgi?id=5939


way...@samba.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED




--- Comment #4 from way...@samba.org  2011-02-22 09:10 CST ---
In the latest code, xattrs are turned off for symlinks on Linux.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

lsetxattr() failed: Operation not permitted on symlinked locked directory

[Nicola Vitacolonna]

Hi,
I am using rsync 3.0.7 from MacPorts under Mac OS X 10.6.4. I am getting the 
error in the subject in the presence of a symlinked and locked directory with 
an extended attribute. To reproduce:

mkdir src
mkdir dst
mkdir src/dir-with-ea-and-uchg
./xattr-util --set mamma.mia How about a nice pizza? src/dir-with-ea-and-uchg
cd src
ln -s dir-with-ea-and-uchg/ symlink-to-dir
chflags uchg dir-with-ea-and-uchg/
cd ..
rsync -avNHAX --fileflags --force-change src/ dst

xattr-util is a utility that I have found at 
http://www.bombich.com/groups/ccc/wiki/7ba51/, but any method to add an 
extended attribute will do. This is the output:

sending incremental file list
./
symlink-to-dir - src/dir-with-ea-and-uchg/
dir-with-ea-and-uchg/
rsync: rsync_xal_set: lsetxattr(dir-with-ea-and-uchg,mamma.mia) failed: 
Operation not permitted (1)
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: lsetxattr() failed: Operation not permitted on symlinked locked directory

[Nicola Vitacolonna]

Sorry, somehow I have screwed up my previous message. In the end, I was asking 
whether the reported behaviour is reproducible and whether it is a bug. If not, 
how can I fix the problem?

Nicola
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Cannot delete non-empty directory/Operation not permitted with file-creation on target-server

[Carsten Deibert]

Hello Everybody,
 
I was searching for an answer myself for quite some time without success, so
I hope somebody can clarify...I use rsync to sync webcontent from one server
to another.

Apache-details:

* Apache runs as nobody:nogroup. 
* Source-Server-Rights htdocs: The rsync-user gains access via o+rx
* Destination-Server-Rights htdocs: The rsync-user is in the group
'nogroup', gains access via owner rsync-user and g+rwx, htdocs-group is
'nogroup'

I use the following command:

/usr/bin/rsync -topglrcze ssh --delete --force --exclude='example.zip'
/vol/www/example/htdocs/ u...@destination-server:/vol/www/example/htdocs/
 
This works fine except in the following scenarios:
 
1. On the destination-server in e.g. /vol/www/example/htdocs/test there
already is an 'example.zip' -- I will receive the following error: cannot
delete non-empty directory. I tried to overcome this with a rsync-filter,
but without success. How can I use the exclude-pattern even if such an
excluded file exists on the destination server ?
  
2. Whenever the Apache-Process of the destination server writes in its
webfolder (e.g. /vol/www/example/htdocs/test/example.htm with
nobody:nogroup) the rsync-user, even has full rights via 'nogroup', will
give me an Operation not permitted wth the next synchronisation.

In both cases the problem seems not to be about file or folder rights, it's
about having files on the destination-server, which weren't synced from the
source-server.

Any help greatly appreciated, thanks.

Carsten

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Cannot delete non-empty directory/Operation not permitted with file-creation on target-server

[Matt McCutchen]

On Wed, 2010-07-14 at 09:35 +0200, Carsten Deibert wrote: 
 I was searching for an answer myself for quite some time without success, so
 I hope somebody can clarify...I use rsync to sync webcontent from one server
 to another.
 
 Apache-details:
 
 * Apache runs as nobody:nogroup. 
 * Source-Server-Rights htdocs: The rsync-user gains access via o+rx
 * Destination-Server-Rights htdocs: The rsync-user is in the group
 'nogroup', gains access via owner rsync-user and g+rwx, htdocs-group is
 'nogroup'
 
 I use the following command:
 
 /usr/bin/rsync -topglrcze ssh --delete --force --exclude='example.zip'
 /vol/www/example/htdocs/ u...@destination-server:/vol/www/example/htdocs/
  
 This works fine except in the following scenarios:
  
 1. On the destination-server in e.g. /vol/www/example/htdocs/test there
 already is an 'example.zip' -- I will receive the following error: cannot
 delete non-empty directory. I tried to overcome this with a rsync-filter,
 but without success. How can I use the exclude-pattern even if such an
 excluded file exists on the destination server ?

That message is only a notice, not an error, and I even opposed printing
it by default (https://bugzilla.samba.org/show_bug.cgi?id=3825#c11).  If
you are happy with the behavior you get, you can ignore the message.
Or, you might want --delete-excluded. 

 2. Whenever the Apache-Process of the destination server writes in its
 webfolder (e.g. /vol/www/example/htdocs/test/example.htm with
 nobody:nogroup) the rsync-user, even has full rights via 'nogroup', will
 give me an Operation not permitted wth the next synchronisation.

Ah, but rsync doesn't have full rights: some operations, such as setting
a file's mtime arbitrarily, require ownership of the file and permission
cannot be granted to others.  I consider this a defect in the POSIX
filesystem model.  Typically only the directories are the problem
because an mtime difference on a regular file will trigger rsync to
transfer and recreate it, so --omit-dir-times would stop the errors.

-- 
Matt


-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

DO NOT REPLY [Bug 5939] rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1)

[samba-bugs]

https://bugzilla.samba.org/show_bug.cgi?id=5939


wthr...@mit.edu changed:

   What|Removed |Added

 CC||wthr...@mit.edu




--- Comment #2 from wthr...@mit.edu  2009-07-14 21:59 CST ---
I also see this bug (using --fake-super), including in a nightly build last
week.  I'm actually getting this error on all symlinks I tested (tried broken
and working to both a file and a directory, didn't try different owners).  I
think this is because I'm using an ext3 file system, and it doesn't support
xattrs on symlinks.

I notice that in the code, usually when an xattr change is attempted, if it
fails on a symlink with EPERM, the failure is ignored, but that this check is
not performed for the delete of stat xattr change.  Adding a check makes the
warnings disappear.  I'm not sure if there is a reason for the absence of the
check, but it seems to cause errors even when there should not be any xattrs
set on the link (because the get_stat_xattr function claims there is an xattr
there when it can't read the xattrs).

Anyway, I've written a simple patch adding the check for EPERM on a symlink.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

DO NOT REPLY [Bug 5939] rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1)

[samba-bugs]

https://bugzilla.samba.org/show_bug.cgi?id=5939





--- Comment #3 from wthr...@mit.edu  2009-07-14 22:03 CST ---
Created an attachment (id=4418)
 -- (https://bugzilla.samba.org/attachment.cgi?id=4418action=view)
Patch to ignore delete of stat xattr failures on symlinks


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

DO NOT REPLY [Bug 5939] New: rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1)

[samba-bugs]

https://bugzilla.samba.org/show_bug.cgi?id=5939

   Summary: rsync: delete of stat xattr failed for ... (in backup):
Operation not permitted (1)
   Product: rsync
   Version: 3.0.4
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P3
 Component: core
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
 QAContact: [EMAIL PROTECTED]


I've been having a problem rsync (3.0.3 and I also tried 3.0.5pre2).  I'm
rsyncing to an rsync daemon with fake super = yes in the rsyncd.conf file and
I get many errors like this:

This ONLY happens to symlinks.  Most symlinks are fine. Most of these are
either broken symlinks or symlinks that happen to have a different owner than
what they link to.  I thought this might be the root of the problem so I
created a small test for new symlinks with these attributes but my test worked
without a problem.  Also one of these errors is for a valid symlink that is
owned by the same owner as what it points to and I've been unable to do
anything to fix the error.

Is there something I can do to increase the logging for the daemon so that I
can't figure out exactly what the problem is?

And... yes the file system was mounted with user_xattr.  fake super seems to
work just fine for me with the exception of these errors.

2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/jtest/public_html (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/IDrive (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/KDrive (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/test (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/daycare (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/hosts (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/house.example.com (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/public_html (in backup): Operation not permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/.kde/cache-vex.example.com (in backup): Operation not permitted
(1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/.kde/socket-vex.example.com (in backup): Operation not
permitted (1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/.kde/tmp-vex.example.com (in backup): Operation not permitted
(1)
2008/12/04 13:53:15 [1818] rsync: delete of stat xattr failed for
home/testuser/amazon/startupscript.sh (in backup): Operation not permitted
(1)
2008/12/04 13:53:18 [1818] rsync: delete of stat xattr failed for
var/www/hosts/house.example.com (in backup): Operation not permitted (1)
2008/12/04 13:53:18 [1818] rsync: delete of stat xattr failed for
var/www/hosts/mail.example.com (in backup): Operation not permitted (1)
2008/12/04 13:53:18 [1818] rsync: delete of stat xattr failed for
var/www/hosts/example.com/docs (in backup): Operation not permitted (1)
2008/12/04 13:53:18 [1818] rsync: delete of stat xattr failed for
var/www/hosts/house.example.com/docs/mandriva-one-2007-kde1.iso (in backup):
Operation not permitted (1)
2008/12/04 13:53:18 [1818] rsync: delete of stat xattr failed for
var/www/hosts/mail.example.com2/docs/images (in backup): Operation not
permitted (1)
2008/12/04 13:53:18 [1818] rsync: delete of stat xattr failed for
var/www/hosts/test2.example.com/docs/preschool (in backup): Operation not
permitted (1)
2008/12/04 14:06:22 [1842] rsync: delete of stat xattr failed for
home/testuser/IDrive (in backup): Operation not permitted (1)
2008/12/04 14:06:22 [1842] rsync: delete of stat xattr failed for
home/testuser/KDrive (in backup): Operation not permitted (1)
2008/12/04 14:06:23 [1842] rsync: delete of stat xattr failed for
home/testuser/amazon/startupscript.sh (in backup): Operation not permitted
(1)
2008/12/04 14:06:26 [1842] rsync: delete of stat xattr failed for
var/www/hosts/mail.example.com2/docs/images (in backup): Operation not
permitted (1)
2008/12/04 14:10:14 [1847] rsync: delete of stat xattr failed for
home/testuser/amazon/startupscript.sh (in backup): Operation not permitted
(1)
2008/12/04 14:12:05 [1852] rsync: delete of stat xattr failed for
home/testuser/amazon/startupscript.sh (in backup): Operation not permitted
(1)
2008/12/04 15:43:36 [1891] rsync: delete of stat xattr failed for
home/testuser/amazon/startupscript.sh (in backup): Operation not permitted
(1)
2008/12/04 15:45:07 [1896] rsync: delete of stat xattr failed for
home

DO NOT REPLY [Bug 5939] rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1)

[samba-bugs]

https://bugzilla.samba.org/show_bug.cgi?id=5939





--- Comment #1 from [EMAIL PROTECTED]  2008-12-04 13:52 CST ---
Well I've managed to increase verbosity a little bit and tried rsyncing only
one of the symlinks that was having this problem:

...
recv_file_name(home/testuser/amazon/startupscript.sh)
received 1 names
[generator] flist start=7, used=1, low=0, high=0
[generator] i=7 4 home/testuser/amazon/startupscript.sh mode=0120777 len=35
uid=1000 gid=1000 flags=0
recv_file_list done
recv_generator(home/testuser/amazon,6)
send_files(6, /home/testuser/amazon)
recv_generator(home/testuser/amazon/startupscript.sh,7)
rsync: delete of stat xattr failed for home/testuser/amazon/startupscript.sh
(in backup): Operation not permitted (1)
set modtime of home/testuser/amazon/startupscript.sh to (1228399898) Thu Dec  4
14:11:38 2008
set uid of home/testuser/amazon/startupscript.sh from 0 to 1000
set gid of home/testuser/amazon/startupscript.sh from 0 to 1000
home/testuser/amazon/startupscript.sh
send_files(7, /home/testuser/amazon/startupscript.sh)
touch_up_dirs: home/testuser (1)
generate_files phase=1
send_files phase=1


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Operation not permitted in rsync

[Wayne Davison]

On Sun, Apr 01, 2007 at 09:05:10PM -0500, ying lcs wrote:
 Can you please tell me what is the meaning of the following error message?
 
 rsync: chgrp 
 /media/LINUXBACKUP/backup/sample/sample/mozilla1.5/mozilla/dom/src/data/.svn/text-base/20070227225544.tar.svn-base
 failed: Operation not permitted (1)

That usually means that the user running the rsync doesn't own the
file on the receiving side, so rsync's attempt to change its group
information failed.

..wayne..
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Operation not permitted in rsync

[ying lcs]

Can you please tell me what is the meaning of the following error message?

rsync: chgrp 
/media/LINUXBACKUP/backup/sample/sample/mozilla1.5/mozilla/dom/src/data/.svn/text-base/20070227225544.tar.svn-base
failed: Operation not permitted (1)
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

rsync: chgrp ... Operation not permitted

[Pascal Perez]

Hi all,
I've installed rsync to synchronize my linux box and my PowerBook.
I have a server whose conf file looks like
[letters]
use chroot = yes
uid = www
gid = lha.utils
path = /var/hdb/letters
read only = no
list = yes
auth users = pascal,lha
secrets file = /etc/rsyncd.secret
but when the client tries to write I have:
rsync: chgrp /file/path/here failed: Operation not permitted (a number)
error messages.
I would like to have the distant machine write on the server as the user www 
and group lha.utils, doesn't use chroot say that?

Any help welcome...
Pascal
_
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/

--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: rsync: chgrp ... Operation not permitted

[Wayne Davison]

On Mon, Dec 20, 2004 at 10:18:12PM +0100, Pascal Perez wrote:
 but when the client tries to write I have:
 rsync: chgrp /file/path/here failed: Operation not permitted (a number)

There was a bug in older rsyncs where it would try to set groups that it
was not authorized to set.  Either upgrade, or avoid using (or implying)
the -g option.

..wayne..
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Operation not permitted?

[Max Kipness]

Hello,

Can someone tell me what the problem is here. I am doing an rsync on a
sendmail spool directory to a folder that is a samba mount. Why is rsync
trying to change owner? Does it have to?

I tried manually changing owner (as root) on a file that is sitting on
the samba mount and I got the same operation not permitted error. Does
anybody know why this is? Or do I need to ask in a samba mailling list.

Here is the error:

chown var/spool/mail/[EMAIL PROTECTED] : Operation not permitted
chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted
chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted
chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted

Thanks,
Max
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Operation not permitted?

[Hardy Merrill]

Just a guess, as I'm a Samba newbie, but if you're trying
to *write* to the Samba mount, then the Samba server needs
to give *write* permissions to that filesystem.  On Red Hat
Linux, this is typically done in

  /etc/samba/smb.conf

find the correct share, and look for the 'writable' option.
After making changes, I think you need to restart samba.

Not sure why rsync does a chown.

HTH.

-- 
Hardy Merrill
Red Hat, Inc.

Max Kipness [EMAIL PROTECTED] wrote:
 
 Hello,
 
 Can someone tell me what the problem is here. I am doing an rsync on a
 sendmail spool directory to a folder that is a samba mount. Why is rsync
 trying to change owner? Does it have to?
 
 I tried manually changing owner (as root) on a file that is sitting on
 the samba mount and I got the same operation not permitted error. Does
 anybody know why this is? Or do I need to ask in a samba mailling list.
 
 Here is the error:
 
 chown var/spool/mail/[EMAIL PROTECTED] : Operation not permitted
 chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted
 chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted
 chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted
 
 Thanks,
 Max
 -- 
 To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
 Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Operation not permitted?

[Jim Salter]

How do you have the destination folder mounted?  Is it mounted via SMBFS,
via NFS, or is it a local folder that just also happens to be shared out via
Samba?  If it's mounted via SMBFS and you're authenticating as root when you
mount it, rsync will think that you have root privileges on the folder and
will therefore attempt to duplicate local file ownership conditions at the
remote end.  Very likely (hopefully, even) the samba system / windows system
on the other end of the mount will NOT actually be granting root privileges
to any samba/windows user named root - mine don't even acknowledge the
existence of anyone going by root.

Hope that helped.

Jim Salter
JRS System Solutions

- Original Message -
From: Max Kipness [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 9:18 AM
Subject: Operation not permitted?



Hello,

Can someone tell me what the problem is here. I am doing an rsync on a
sendmail spool directory to a folder that is a samba mount. Why is rsync
trying to change owner? Does it have to?

I tried manually changing owner (as root) on a file that is sitting on
the samba mount and I got the same operation not permitted error. Does
anybody know why this is? Or do I need to ask in a samba mailling list.

Here is the error:

chown var/spool/mail/[EMAIL PROTECTED] : Operation not permitted
chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted
chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted
chown var/spool/mail/[EMAIL PROTECTED]  : Operation not permitted

Thanks,
Max
--
To unsubscribe or change options:
http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Operation not permitted?

[Martin Pool]

On  9 Sep 2003 Max Kipness [EMAIL PROTECTED] wrote:

 Can someone tell me what the problem is here. I am doing an rsync on a
 sendmail spool directory to a folder that is a samba mount. 

What do you mean by a samba mount?  A filesystem mounted over smbfs?

 Why is rsync trying to change owner?

Because you told it to, using the -a, -o or -g options.

 Does it have to?

You asked for it, you got it :-)

 I tried manually changing owner (as root) on a file that is sitting on
 the samba mount and I got the same operation not permitted error.

Assuming you're using smbfs, it's because smbmount logs in to the
server as a single NT user, and all files appear to be owned by that
user.  Ownership is not preserved.

cifsfs may fix this, but you need to ask about that elsewhere.

-- 
Martin 
-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html