similar to: DO NOT REPLY [Bug 5324] New: with option --xattrs the process rsync is more long time

https://bugzilla.samba.org/show_bug.cgi?id=8566 Summary: Spotlight comments (extended attributes) are not synced Product: rsync Version: 3.0.9 Platform: All OS/Version: Mac OS X Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

We are using Samba 4.6.15. We have users not being able to login. winbindd log shows this: [2018/06/14 14:48:44.300203, 0, pid=3228] ../source3/rpc_client/cli_pipe.c:3292(cli_rpc_pipe_open_schannel_with_creds) netlogon_creds_cli_get returned NT_STATUS_UNSUCCESSFUL [2018/06/14 14:53:43.896350, 0, pid=3228] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)

https://bugzilla.samba.org/show_bug.cgi?id=5365 Summary: --backup and --xattrs are not compatible Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: fauthier@free.fr

On 6/30/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > checksum-xattr.diff > Log Message: > A simple patch that lets rsync use cached checksum values stored in > each file's extended attributes. A perl script is provided to create > and update the values. Wayne, You should be aware of two drawbacks of caching checksums in xattrs: First,

Hi folks, I wish you all a happy new year! I want to migrate a fileserver for Windows und MAC OS clients with ancient versions of samba and netatalk to samba 3.6 (with a samba 4 domain controller), but this raises quite some issues. The new server should - if possible - not be running netatalk. While the package is quite mature, being able to access the same share with both CIFS and AFS

In ctime updating of xattr, it use the wrong type of access for inode, so use ocfs2_journal_access_di instead. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/xattr.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c index 915039f..e393315 100644 --- a/fs/ocfs2/xattr.c +++ b/fs/ocfs2/xattr.c @@ -2592,8 +2592,9 @@

Hi! I'm new here, so I ask for your patience :) Some xattrs can't be copied between filesystems. For instance, compressed btrfs has a "btrfs.compression" xattr. When rsync -X is used in this situation, it exits with error code 23 (partial file/attr), which seems dangerous to be ignored. Would it be reasonable to filter filesystem-specific flags when transferring to a different

I see that rsync will eventually support extended attributes, which will be great. But: will it allow backup from a file system that supports xattrs, to one that does not? For this to work, rsync would have to represent the xattrs on the destination machine in some special format, I suppose, which is outside the usual rsync mode of operation. Moreover, even if both machines support

Currently, when listing xattrs, kernel define XATTR_LIST_MAX as 65536 in include/linux/limits.h, so it can't handle too many xattrs. But with ocfs2 xattr tree, we actually have no limit for the number. And it will pollute the message with something like this when listing. (27738,0):ocfs2_iterate_xattr_buckets:3158 ERROR: status = -34 (27738,0):ocfs2_xattr_tree_list_index_block:3264 ERROR:

On Fri, Mar 24, 2023 at 9:26?AM Roberto Sassu <roberto.sassu at huaweicloud.com> wrote: > > On Fri, 2023-03-24 at 11:18 +0100, Roberto Sassu wrote: > > On Thu, 2023-03-23 at 20:09 -0400, Paul Moore wrote: > > > On Tue, Mar 14, 2023 at 4:19?AM Roberto Sassu > > > <roberto.sassu at huaweicloud.com> wrote: > > > > From: Roberto Sassu

On Fri, 2023-03-24 at 17:39 -0400, Paul Moore wrote: > On Fri, Mar 24, 2023 at 9:26?AM Roberto Sassu > <roberto.sassu at huaweicloud.com> wrote: > > On Fri, 2023-03-24 at 11:18 +0100, Roberto Sassu wrote: > > > On Thu, 2023-03-23 at 20:09 -0400, Paul Moore wrote: > > > > On Tue, Mar 14, 2023 at 4:19?AM Roberto Sassu > > > > <roberto.sassu at

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,

On Fri, Mar 24, 2023 at 6:18?AM Roberto Sassu <roberto.sassu at huaweicloud.com> wrote: > On Thu, 2023-03-23 at 20:09 -0400, Paul Moore wrote: > > On Tue, Mar 14, 2023 at 4:19?AM Roberto Sassu > > <roberto.sassu at huaweicloud.com> wrote: > > > From: Roberto Sassu <roberto.sassu at huawei.com> > > > > > > Currently,

I recently found a bug in the xattrs patch, where it would apply the wrong xattrs to some files in a transfer. While looking at the code, I think I found another one (it sure looks wrong, but I haven't figured out how to demonstrate it yet). Anyway, here's the patch: The first hunk fixes the apparent bug. The second hunk fixes the demonstratable bug. I haven't (yet) looked to see

On 01/06/2017 12:27 AM, L. A. Walsh wrote: > Stefan Berger wrote: >> 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. > --- (see below "...")... > > Please put this on a switch or option. > > The security.evm field seems only special on

I compiled 3.0.6pre1, including the crtimes and fileflags patches for use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here: <http://www.bombich.com/mactips/rsync.html> I want to use 3.0.6 because it seems that this bug: <https://bugzilla.samba.org/show_bug.cgi?id=5365> has been resolved (yay!). ----- [~]$ rsync --version rsync version 3.0.6pre1 protocol version 30

I'm using rsync 3.0.7 on Mac OS X 10.6, compiled according to Mike Bombich's instructions at http://www.bombich.com/rsync.html. Rsync repeatedly exits with a protocol data stream error when trying to copy some com.apple.FinderInfo extended attributes. While testing this issue, I found that rsync is not actually copying all extended attributes even when there is no error message. I'm

From: Roberto Sassu <roberto.sassu at huawei.com> One of the major goals of LSM stacking is to run multiple LSMs side by side without interfering with each other. The ultimate decision will depend on individual LSM decision. Several changes need to be made to the LSM infrastructure to be able to support that. This patch set tackles one of them: gives to each LSM the ability to specify one

Hello. On May 22, someone reported that xattrs don't work right with --link-dest on rsync 3.0.0cvs: http://lists.samba.org/archive/rsync/2007-May/017768.html I've run into the same problem, but on Red Hat Enterprise Linux 5: # rsync --version rsync version 2.6.8 protocol version 29 Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others. <http://rsync.samba.org/>

https://bugzilla.samba.org/show_bug.cgi?id=5298 Summary: xattrs and acls do not work well together along with fake-super, even worse on XFS Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: