similar to: Rsync ACLs over NFSv4 to EXT4 - rsync_xal_set: lsetxattr - Operation not supported

Displaying 20 results from an estimated 200 matches similar to: "Rsync ACLs over NFSv4 to EXT4 - rsync_xal_set: lsetxattr - Operation not supported"

2015 Mar 11
0
Rsync ACLs over NFSv4 to EXT4 - rsync_xal_set: lsetxattr - Operation not supported
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xattrs are not supported via NFS: http://comments.gmane.org/gmane.linux.nfs/53259 I would suggest letting rsync do the networking between the Linux systems (probably over ssh). This will also prevent you from being stuck in --whole-file. On 03/11/2015 09:41 AM, Andrew LaPierre wrote: > I think this is an NFS or ext4 question, but wanted to post
2020 May 12
1
[Bug 14377] New: rsync rsync_xal_set lsetxattr failed invalid argument
https://bugzilla.samba.org/show_bug.cgi?id=14377 Bug ID: 14377 Summary: rsync rsync_xal_set lsetxattr failed invalid argument Product: rsync Version: 3.1.3 Hardware: All OS: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayne at opencoder.net
2006 Apr 19
4
DO NOT REPLY [Bug 3701] New: rsync_xal_set: lsetxattr system.posix_acl_default failed: Permission denied
https://bugzilla.samba.org/show_bug.cgi?id=3701 Summary: rsync_xal_set: lsetxattr system.posix_acl_default failed: Permission denied Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:
2017 Dec 18
0
Centos7: backup with rsync problem: "rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/fstab"", "security.selinux") failed: Permission denied (13)"
If I run this command in order to backup /etc from remote server to local dir I get a lot of this message: [root at s-virt tmp]# rsync -a --delete --numeric-ids --relative --delete-excluded --compress --acls --xattrs rsync://server-dati/root/etc/ /tmp/test/ -v receiving incremental file list rsync: rsync_xal_set:
2010 Aug 27
0
rsync_xal_set failed : Operation not supported
Hi guys, I have a question about this error. It occurs for some files when I try to backup a file server running Samba on FreeBSD, using aHAXR rsync options. The exact error is : rsync_xal_set: lsetxattr("****","user.SAMBA_PAI") failed: Operation not supported (95) (stars are a real path I cannot provide) The source file is located on a read-only mounted volume
2010 Nov 11
1
lsetxattr() failed: Operation not permitted on symlinked locked directory
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
2009 Dec 22
3
XAPI source code
Hi All I have downloaded the opensource xapi source code. I am not sure what the functins of the follow modules: 1 block_device_io 2 datamodel 3 xiu (I am puzzled by the name "xiu") 4 stats 5 rpc-light 6 rss 7 xb (I think the xapi needs not to talk to xenbus directly) 8 xsrpc (why it writes some "rpc" keys to path of "domain/<domid>" in the
2007 Oct 21
2
xattrs: Permission denied?
I've found a(nother) bug with the xattr code: kiwiw:~/x terpstra$ uname -a Darwin kiwiw.lan 8.10.0 Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC Power Macintosh powerpc kiwiw:~/x terpstra$ echo test > bar kiwiw:~/x terpstra$ xattr --set broken demo bar kiwiw:~/x terpstra$ chmod 0444 bar kiwiw:~/x terpstra$ rsync-3.0 -aHAXSx bar
2007 Oct 17
0
xattrs on symlinks
As we all know, only osx supports xattrs on symlinks. Unfortunately, not only does osx support xattrs on symlinks, *every* symlink has, at the least, com.apple.FinderInfo. When backing up to a linux system, this results in one error message per symlink: rsync: rsync_xal_set: lsetxattr("User Guides And Information","user.com.apple.FinderInfo") failed: Operation not
2007 Nov 15
2
rsync error?
Hi Folks Can anyone help me with the following error - is it serious; is the file transferred; are the other files transferred? [morgan@morgansmachine ~]$ rsync -a -X -A -z -v /home/morgan/Documents 192.168.1.30:/home/morgan/Documents morgan@192.168.1.30's password: building file list ... done rsync: rsync_xal_set:
2016 Dec 01
3
[PATCH v2 1/2] xattrs: Skip security.evm extended attribute
The security.evm extended attribute is fully owned by the Linux kernel and cannot be directly written from userspace. Therefore, we can always skip it. --- xattrs.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/xattrs.c b/xattrs.c index b105392..3b72e61 100644 --- a/xattrs.c +++ b/xattrs.c @@ -255,6 +255,9 @@ static int rsync_xal_get(const char *fname,
2014 Feb 02
1
Bugg when using Extended Attributes flag -X
Hello, I found that using rsync on OS X can give some problems when it comes to Extended Attributes (-X flag). The server I use has Ubuntu with the filesystem XFS and I am trying to backup a OS X system to it. The problem is as far as I understand it that Linux Kernel has a liming on 64k f?r Extended Attributes and OS X don?t have this limit. Some error output. rsync: rsync_xal_set:
2009 Apr 03
1
"Invalid argument (22)" & "Operation not supported (95)" ???
Hi Folks I've gone back over the list and the only reference I've found to "Invalid argument (22)" is here: http://lists.samba.org/archive/rsync/2006-May/015478.html That seems a different context of character set mismatches. The common parts to my errors are: rsync: rsync_xal_set: lsetxattr("...","security.selinux") failed: Invalid argument (22) And:
2007 Oct 30
1
Rsync 3.0.0pre4 errors with ACLs and Xattrs between OSX and Linux
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's my understanding that as of 3.0 rsync supports OS X ACLs and extended attributes, and that it should be possible to backup a tree from an OS X system that contains files and folders with ACLs and extended attributes to a Linux host filesystem that has both "user_xattrs" and "acl" enabled on the destination file system.
2009 Oct 28
1
Operation not supported (95)
Hi guys, I'm running into a problem that I'm sure which part of the process fails. I use wget (OSX Leopard, wget 3.0.6 compiled from source) to backup my ~/Pictures directory to a linux server, also with wget 3.0.6 (Debian). In persuit of being sure I get everything from HFS filesystem (resource fork/metadata), I'm getting the following error: rsync: rsync_xal_set:
2008 Apr 14
0
[PATCH] xattrs not set on locked files that already exist on target
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:
2009 Jul 17
1
Voicemail ODBC storage table schema
Hello, Upgraded from 1.6.1.0 to 1.6.1.1 and my voicemail setup does not work anymore. I use ODBC storage for voicemail. Comes out that the "voicemessages" table schema should have changed, because the log says Asterisk needed to store data to an additional field called "flag". Any new message cannot be saved. The thing is that I'd like to know where I can find an updated
2007 Mar 08
3
[BUG] clear ACL-s on destination
Destroy ACL-s on destination when no ACL-s differens between source and destination. Bug is somehow related with function send_file_name() called with negative file descriptor f. There is no such bug in 2.6.9 version, but there options "-X -A --deleted" can't be used (we have "Internal error: wrong write used in receiver."). If I fix this, avoid calling send_acl() &
2008 Jun 25
2
DO NOT REPLY [Bug 5565] New: xattrs not set on locked files that already exist on target
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
2017 Nov 01
2
some problem by use libopusenc
1,you say “libopusenc depends only on libopus.”but 2,so,i add speexdsp source code , but 3,so,i 。。。 but now,what can i do。i use libopus 1.2 and 1.2beta and 1.1.3 test -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20171101/40680ea1/attachment-0001.html> -------------- next part -------------- A