similar to: xattrs questions

Hello group, I have an OSX 10.3.9 Server that I'm trying to back up with rsync 3.0.2. Since I didn't have any luck with the 10.3.9 patch and I do have 10.4 clients, I decided to try running the backup over AFP (Apple's file sharing protocol). I found a way to mount the AFP volume with root permissions and rsync 3.0.2 works very nicely using this on the 10.4 clients, preserving

I am using the latest 3.0.0cvs protocol version 30 Capabilities: 64- bit files, 32-bit system inums, 64-bit internal inums, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, no ACLs, xattrs xattrs cvs 1.77 I installed xattr for Mac OSX Senario: $ mkdir /Users/alan/Desktop/folder1 $ echo 'Hello' > /Users/alan/Desktop/folder1/file1 $ xattr --set color blue

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

-----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.

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:

Hi. I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. I confirmed that ResourceFork and FinderInfo are compatible with Netatalk 3.1.7. However, EAs are incompatible. The character ":" in EA name is wrong. The EAs are not seen from clients. smb.conf: [test2] path = /export/test2 writable = yes vfs objects = catia fruit streams_xattr fruit:locking =

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

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'm trying to get an old FreeBSD 4.11 server to talk to a newer FreeBSD 7 server that is running rsync 3.0.4 but I am running into an error with extended file attributes: Basic steps: Applied the fileflags patch per the instructions: patch -p1 <patches/fileflags.diff ./prepare-source Ran the following configure line: ./configure --with-included-popt --disable-iconv

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:

https://bugzilla.samba.org/show_bug.cgi?id=5324 Summary: with option --xattrs the process rsync is more long time 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

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

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

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

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

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

Hello, This is the little basic program I used to test xattrs. First thing I did was something like this cd /mnt/btrfs-test for i in $(seq 0 100000); do touch file_$i; done and then run time ./xattr-test /mnt/btrfs 0 time ./xattr-test /mnt/btrfs 1 time ./xattr-test /mnt/btrfs 2 the 0 test creates 100 xattrs for every file in the directory. the 1 test just does a listxattr for every file in

Hi HAT! Nice to meet you over here... ;) On Wed, Mar 11, 2015 at 11:30:45PM +0900, HAT wrote: > Hi. > I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. > I confirmed that ResourceFork and FinderInfo are compatible with > Netatalk 3.1.7. However, EAs are incompatible. > The character ":" in EA name is wrong. > The EAs are not seen from clients. >

On Tue, Jul 28, 2015 at 02:55:32PM +0200, Michal Moravec wrote: > 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