similar to: xattr version generates 'wrong write used in receiver'

Hi, I'm using 2.6.9 but I get: recv_files phase=1 generate_files phase=2 recv_files phase=2 recv_files finished generate_files phase=3 deleting in home delete_in_dir(home) [generator] make_file(home/administ,*,2) Internal error: wrong write used in receiver. _exit_cleanup(code=2, file=io.c, line=1204): entered _exit_cleanup(code=19, file=main.c, line=1182): entered rsync error: received

Working with rsync 3.0.2, it appears that rsync isn't unlocking files before setting the file attributes when those files already exist. This generates error messages on subsequent such as: rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed: Operation not permitted (1) rsync: rsync_xal_clear:

Thanks for the help on the missing '-p1' for the acl and xattr patches. Things are configuring and making properly now. However, I couldn't help noticing this during the configure: checking whether to support ACLs... ACLs requested -- running tests checking for acl_get_file in -lacl... no checking for ACL support... yes checking ACL test results... Using posix ACLs checking for

Hi, We are updating KubeVirt to libvirt 5.6.0. Before that we were running on 5.0.0. It seems like something regarding setting xattrs on files has changed, because with libvirt 5.6.0 we are getting the following error: ``` Unable to set XATTR trusted.libvirt.security.dac on /var/lib/libvirt/qemu/domain-410-default_vmi-fedora: Operation not permitted') ``` The main problem is for us is that

On Thu, 2022-12-01 at 11:41 +0100, Roberto Sassu wrote: > From: Roberto Sassu <roberto.sassu at huawei.com> > > Currently, evm_inode_init_security() processes a single LSM xattr from > the array passed by security_inode_init_security(), and calculates the > HMAC on it and other inode metadata. > > Given that initxattrs() callbacks, called by >

Hi, I have recently downloaded the rsync-3.0.0pre5 and wanted to see how it works (especially xattr feature).. I did following steps.. ./configure make make test make test shows following tests skipped.. SKIP xattrs (Unable to set an xattr) from 3.0 i have read that xattr support is by default and there is no specific patch is required to use this feature.. I want to know how the xattr

Does rsync support acl and xattr (as with acl and user_xattr mount options)? I saw some acl patches for rsync, so probably it's not officially blessed yet. However, I didn't see any xattr patches - although some talks about it on the list go back into year 2003. So how it is with support for these? If I backup a Samba server, which has a filesystem mounted with acl,user_xattr (with

Hello, As i cannot get 3.0.0pre5 to work in my environment (throwing crazy errors which i've posted previously), i would like to revert to 2.6.9 . Of course, the reason i tried to use v3 in the first place was for the acl, xattr, and fake-super options - which, evidently, can be enabled under 2.6.9, as per the following sources: http://lists.samba.org/archive/rsync/2007-February/017218.html

Modification from V2 to V3: Use a more pefect code suggested by Joel. Thank Joel for it. In ocfs2/xattr, we must make sure the xattrs which have the same hash value exist in the same bucket so that the search schema can work. But in the old implementation, when we want to extend a bucket, we just move half number of xattrs to the new bucket. This works in most cases, but if we are lucky enough we

https://bugzilla.samba.org/show_bug.cgi?id=6590 Summary: [sender] could not find xattr #1 for home/jdoe/TheFresh Product: rsync Version: 3.0.5 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: stlman at

https://bugzilla.samba.org/show_bug.cgi?id=5565 Summary: xattrs not set on locked files that already exist on target Product: rsync Version: 3.0.3 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=10357 Summary: make check fails for xattr tests Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: psimerda at redhat.com

Is there option for deleting xattr-s same as --delete for files, because it seems deletion of xattr don't sync, however it is synced when data of file change, see example below. Maybe this is a bug or maybe this is ok? System gentoo attr-2.4.32, rsync form today cvs. -- Regards Stanislaw Gruszka stasiu@sg /mnt/hda5/export $ echo "data" > file stasiu@sg /mnt/hda5/export $

Hi, Thanks Tao and Joel's review, These are the second version of the patches. Mark and Joel, you can correct my comments if you find they don't suitable. thanks, tiger

If one is rsyncing a machine without selinux (therefore no security.selinux xattr on each file), to a system that has selinux (even in permissive mode), rsync doesn't play nice. basically selinux seems to make it appear that every file has security.selinux xattr on each file (I think this is virtually if there's no physical attribute, as if one disables selinux, the attribute disappears).

Move all the common code to a new _getxattr function, much like done for other xattrs operations. Mostly code motion, no functional changes. --- daemon/xattr.c | 54 +++++++++++------------------------------------------- 1 file changed, 11 insertions(+), 43 deletions(-) diff --git a/daemon/xattr.c b/daemon/xattr.c index abed5ff..d8ad59a 100644 --- a/daemon/xattr.c +++ b/daemon/xattr.c @@ -55,6

https://bugzilla.samba.org/show_bug.cgi?id=3172 ------- Additional Comments From vapier@gentoo.org 2005-10-15 20:47 ------- Created an attachment (id=1516) --> (https://bugzilla.samba.org/attachment.cgi?id=1516&action=view) test.log -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact

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:

Hello I am trying to integrate OS X 10.10.4 clients into existing Samba infractructure run by our IT department. We are currently using Samba 4.2.3. File share is stored on iSCSI array with ext4 filesystem which should support both ACL and XATTR. We are trying to setup vfs_fruit module to avoid possible performance problems on OS X clients. We do NOT user netatalk. Current vfs_fruit config:

https://bugzilla.samba.org/show_bug.cgi?id=10925 Bug ID: 10925 Summary: non-atomic xattr replacement in btrfs => rsync --read-batch random errors Product: rsync Version: 3.1.0 Hardware: All URL: http://article.gmane.org/gmane.comp.file-systems.btrfs /40013 OS: All