search for: setfattr

Can I use a command like this to clone an NT ACL? getfattr -n security.NTACL templateFile | sed -e 's/templateFile/realFile/' | sudo setfattr --restore=- I can see that the attribute gets copied over but when I view the ACL in Windows security tab it's not the same ACL, it's much bigger and includes all kinds of default-like stuff. I'm trying to find a way to update permissions on a mass amount of files without using the...

Hello I have two peers setup and working with x2 bricks each. They have been working via tcp for the last 4-5 months. I just got two Infiniband cards and put the on the peers. I want to change the transport type to rdma instead of tcp but I don't see an easy way to do this. Can you please help me with proper instructions. Best Regards Ivan Dimitrov

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

On 03/24/2018 08:20 PM, Ken McDonald via samba wrote: > Can I use a command like this to clone an NT ACL? > > getfattr -n security.NTACL templateFile | sed -e > 's/templateFile/realFile/' | sudo setfattr --restore=- > > I can see that the attribute gets copied over but when I view the ACL > in Windows security tab it's not the same ACL, it's much bigger and > includes all kinds of default-like stuff. I'm trying to find a way to > update permissions on a mass amount of...

Hello, I've removed a volume and I can't re-create it : gluster volume create gluster-export gluster-6:/export gluster-5:/export gluster-4:/export gluster-3:/export /export or a prefix of it is already part of a volume I've formatted the partition and reinstalled the 4 gluster servers and the error still appears. Any idea ? Thanks. -- -------------- next part --------------

Hi all, Running into a problem with my gluster here in a LAB env. Production is a slightly different build(distributed replicated with multiple arbiter bricks) and I don't see the same errors...yet. I only seem to have this problem on 2 client vm's that I ran "setfattr -n trusted.io-stats-dump -v output_file_id mount_point" on while trying to test for latency issues. Curious if anyone has run into a similar situation with the bad file descriptor mess below and knows what I'm doing wrong or missing, besides everything... I had built this gluster in one l...

...ank you for info. >> fruit:nfs_aces = yes >> fruit:veto_appledouble = yes > > fwiw, I'd remove anything that is the default. Are there any possible problems with this approach apart from convention/cleaner config? Our Samba admin prefers it this way. > man setfattr admin-apple # touch test.txt admin-apple # setfattr -n user.test -v test test.txt admin-apple # setfattr -n security.test -v test2 test.txt admin-apple # getfattr -d test.txt # file: test.txt user.test="test" admin-apple # getfattr -n security.test -d test.txt # file: test.txt security.t...

...xt4 and xattr and acl are not set, as they are default for ext4. 19:06:17 # more /boot/config-3.16.0-4-amd64 | grep CONFIG_EXT4 CONFIG_EXT4_FS=m CONFIG_EXT4_USE_FOR_EXT23=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set After install of package attr tests with setfattr and getfattr succeed. Do I still need CONFIG_EXT4_FS_XATTR=y ? If yes, how do I enable that in the kernel? kind regards, birgit

...CONFIG_OCFS2_FS_STATS is not set # CONFIG_OCFS2_DEBUG_MASKLOG is not set # CONFIG_OCFS2_DEBUG_FS is not set CONFIG_OCFS2_FS_POSIX_ACL = y at least the attr (5) does not appear to work mount ....... dev/loop0 on / tmp/ocfs2 type ocfs2 (rw, user_xattr, acl, heartbeat = none) cd / tmp/ocfs2 touch xx setfattr-n security.selinux-v unconfined_u: object_r: user_tmp_t: s0 xx setfattr: xx: Operation not supported Thanks in advance -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20100303/5dc81009/attachment.html

...slave it is not accessible); - stop gluster software on master (already stopped on slave); - remove gluster software on master and slave (previous administrator used own built rpms, I would like to use http://download.gluster.org/pub/gluster/glusterfs/3.3/3.3.1/EPEL.repo/); - clean old information: setfattr -x trusted.glusterfs.volume-id /gluster setfattr -x trusted.gfid /gluster rm -rf /gluster/.glusterfs - rsync data from master to slave; - start gluster and create a volume with data in rsynced /gluster directory. Are there any pitfalls I should know about? Best regards, Rafal Radecki.

...slave it is not accessible); - stop gluster software on master (already stopped on slave); - remove gluster software on master and slave (previous administrator used own built rpms, I would like to use http://download.gluster.org/pub/gluster/glusterfs/3.3/3.3.1/EPEL.repo/); - clean old information: setfattr -x trusted.glusterfs.volume-id /gluster setfattr -x trusted.gfid /gluster rm -rf /gluster/.glusterfs - rsync data from master to slave; - start gluster and create a volume with data in rsynced /gluster directory. Are there any pitfalls I should know about? Best regards, Rafal Radecki.

...trusted.afr.dirty=0x000000000000000000000001 Since Node3(the arbiter) sees it as dirty and it looks like Node 1 and Node 2 have good copies, I was thinking of running the following on Node1 which I believe would tell Node 2 and Node 3 to sync from Node 1 I'd then kick off a heal on the volume setfattr -n trusted.afr.volume-client-1 -v 0x000000010000000000000000 /path/to/dir setfattr -n trusted.afr.volume-client-2 -v 0x000000010000000000000000 /path/to/dir client-0 is node 1, client-1 is node2 and client-2 is node 3. I've verified the hard links with gfid are in the xattrop directory Is this...

Hi, I am trying to understand how the extended attribute trusted.io-stats-dump works. setfattr -n trusted.io-stats-dump -v /tmp/gluster_perf_stats/io-stats-pre.txt /mnt/gluster/gv0_glusterfs I can see that the io-stats-pre.txt is created. But how and what happened in the background? And why I can't I see the attribute with getfattr again? getfattr -dm- /mnt/gluster/gv0_glusterfs # fil...

...T %ZPAR% /LOG+:%log% When I do the same to my Samba, I get a lot of "ERROR 5 (0x00000005) Changing File Attributes" errors. I run Samba on ZFS on Linux in a container, Proxmox based. xattrs seem to work: root at nas2:/mp0/storage/backup# touch userattr root at nas2:/mp0/storage/backup# setfattr -n user.steffen -v washere userattr # file: userattr user.steffen="washere" but not for security: root at nas2:/mp0/storage/backup# touch secattr root at nas2:/mp0/storage/backup# setfattr -n security.NTACL -v 1 secattr setfattr: secattr: Operation not permitted (the same works on the...

...ftpVol 4. Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y volume delete: eftpVol: success gluster> peer status Number of peers: 0 5. Remove gluster-related configurations. brick_path=/gluster/eftpbrick [ -d $brick_path ] && setfattr -x trusted.glusterfs.volume-id $brick_path [ -d $brick_path ] && setfattr -x trusted.gfid $brick_path [ -d $brick_path/.glusterfs ] && rm -rf $brick_path/.glusterfs 6. # systemctl stop glusterd.service 7. # systemctl start glusterd.service Steps for gluster conf...

...t with libguestfs and don't need to automate the process (ie. you're only doing it one-off for a few disks), then it's better to use virt-rescue. Something like this: $ virt-rescue -a thedisk ><rescue> mount /dev/sda2 /sysroot ><rescue> cd /sysroot ><rescue> setfattr -h -v 0x00000000 -n system.ntfs_attrib directory-name (See also: http://www.tuxera.com/community/ntfs-3g-advanced/data-compression/) You can also use the regular getfattr command to list the attribute, although the format seems to need a bit of decoding: ><rescue> mkdir compressed >&...

...n=AD > Administrator password will be set randomly! > You are not root or your system do not support xattr, using tdb > backend for attributes. Aside: the zfs "xattr" property is already on by default. Inside the container it works for me with user xattrs: root at wrn-dc1:~# setfattr -n user.bar -v baz /tmp/foo root at wrn-dc1:~# getfattr -n user.bar /tmp/foo getfattr: Removing leading '/' from absolute path names # file: tmp/foo user.bar="baz" But when I strace "samba-tool domain provision": open("/usr/local/samba/tmpE7Z_yH", O_RDWR|O_CR...

...16733-500G..etc set acls: /usr/local/samba/bin/samba-tool ntacl set ?O:S-1-5-21-1345677-xxxxx-2594716733-500G..etc? /${EXT4 Sharename}/Lou/stuff/ ...after which I update the smb.conf entry and can browse the folder as normal, as long as it stays on the EXT4-backed share. The acl-compliance tests: setfattr -n user.test -v test test.txt setfattr -n security.test -v test2 test.txt getfattr -d test.txt ...return the correct results on both filesystems; EXT4 and ZFS. Samba is running in stdout debug more: sudo /usr/local/samba/sbin/samba -i -M single and throws no errors during the course of the problem...

Hi, I would like to set filesystem permissions on shares (users, at the moment) with Windows 10 (1809). On the Samba side, the filesystem is ext4. I tested the extended attributes usability with setfattr/getfattr, and setfacl/getfacl, and they work. I set the followings in smb.conf: [global] vfs objects = acl_xattr map acl inherit = yes store dos attributes = yes ... [users] path = /home/users read only = no And: chown root:"Domain Admins" /home/users chmod 0770 /home/users I gave SeDi...

...ReportedBy: pierre@tuxfamily.org QAContact: rsync-qa@samba.org When I try to use -X option with a patched rsync (using XFS as file system), I obtain this when a file have multiple user attributes: [root@Chakra data]# echo "test" > test_pierre/test.file [root@Chakra data]# setfattr -n user.test1 -v testval1 test_pierre/test.file [root@Chakra data]# setfattr -n user.test2 -v testval2 test_pierre/test.file [root@Chakra data]# getfattr test_pierre/test.file # file: test_pierre/test.file user.test1 user.test2 [root@Chakra data]# rsync -AavX -P -W --numeric-ids --delete --forc...