search for: setxattr

Hi All, Does anybody know how to use the getxattr/setxattr commands in guestfish? It seems not working for ext2/3 filesystem. I did not find the corresponding commands in bash either. So is it for xfs only? Regards, Pengzhen Cao

...> list any errors so far and the numbers look like realistic values. > But we're seeing some strange errors (every few minutes) reports in the > journald: > ?[2018-04-23 12:31:24.942377] E [MSGID: 113001] > [posix.c:5983:_posix_handle_xattr_keyvalue_pair] 0-$myvolume-posix: > setxattr failed > on /srv/glusterfs/bricks/DATA112/data/.glusterfs/e6/a8/ > e6a8ce50-fda5-4bad-8d4d-acd25dafcaa2 while doing xattrop: > key=trusted.glusterfs.quota.1ce02d3b-b7ae-4485-903c-2991de5350b6.contri.1 > [No such file or directory]? > The rebalance log file lists no errors. > >...

...> list any errors so far and the numbers look like realistic values. > But we're seeing some strange errors (every few minutes) reports in the > journald: > ?[2018-04-23 12:31:24.942377] E [MSGID: 113001] > [posix.c:5983:_posix_handle_xattr_keyvalue_pair] 0-$myvolume-posix: > setxattr failed > on /srv/glusterfs/bricks/DATA112/data/.glusterfs/e6/a8/ > e6a8ce50-fda5-4bad-8d4d-acd25dafcaa2 while doing xattrop: > key=trusted.glusterfs.quota.1ce02d3b-b7ae-4485-903c-2991de5350b6.contri.1 > [No such file or directory]? > The rebalance log file lists no errors. > >...

...$myvolume status? doesn't list any errors so far and the numbers look like realistic values. But we're seeing some strange errors (every few minutes) reports in the journald: ?[2018-04-23 12:31:24.942377] E [MSGID: 113001] [posix.c:5983:_posix_handle_xattr_keyvalue_pair] 0-$myvolume-posix: setxattr failed on /srv/glusterfs/bricks/DATA112/data/.glusterfs/e6/a8/e6a8ce50-fda5-4bad-8d4d-acd25dafcaa2 while doing xattrop: key=trusted.glusterfs.quota.1ce02d3b-b7ae-4485-903c-2991de5350b6.contri.1 [No such file or directory]? The rebalance log file lists no errors. Has anybody seen similar error mess...

...defines the maximum permissions and so since touch uses the 0666 create mode, the exec bit is not set. So far so good. Now to samba. The share has these controls: ... create mask = 0664 ... When stracing the samba process, I see that 0664 is specified in the open system call, but following that, setxattr is called (not sure by samba or some kernel process), which must be setting the exec bit on the group? ... 96012 open("new", O_RDWR|O_CREAT|O_EXCL, 0664) = 40 96012 setxattr("New Text Document.txt", "system.posix_acl_access", LONG_HEX_STRING_HERE, 52, 0) = 0 ... My...

...45,8 +545,98 @@ do_lgetxattr (const char *path, const char *name, size_t *size_r) > return buf; /* caller frees */ > } > > +int > +copy_xattrs (const char *src, const char *dest) > +{ > +#if defined(HAVE_LISTXATTR) && defined(HAVE_GETXATTR) && defined(HAVE_SETXATTR) I wonder if there are any platforms that lack one of listxattr, getxattr and setxattr, but at the same time have one of these calls. The xattr code (in general) is incredibly complex because of all these tests. I guess Mac OS X probably has none of them, and RHEL 5 / Ubuntu 10.10 probably had on...

Hi, attached there is a prototype of patch for adding a new copy-attributes command. Such command would allow copy the attributes of a "file" to another, so for example in guestfish: copy-attributes foo bar permissions:true xattributes:false would only copy the permissions of foo to bar, not copying its extended attributes too. Just few notes: - my first daemon command, so

...+ attrval = new; + attrval_len = vlen; + } + + CHROOT_IN; + vlen = getxattr (src, &buf[i], attrval, vlen); + CHROOT_OUT; + if (vlen == -1) { + reply_with_perror ("getxattr: %s, %s", src, &buf[i]); + goto error; + } + + CHROOT_IN; + ret = setxattr (dest, &buf[i], attrval, vlen, 0); + CHROOT_OUT; + if (ret == -1) { + reply_with_perror ("setxattr: %s, %s", dest, &buf[i]); + goto error; + } + } + + return 1; + + error: + return 0; +} + #else /* no HAVE_LINUX_XATTRS */ OPTGROUP_LINUXXATTRS_NOT_AVAILABL...

Hi Louis, On Wed, Apr 22, 2015 at 01:15:21PM +0200, L.P.H. van Belle wrote: > Or.. > get the sources and recompile agains 14.04 > > use the following commands. > enable the deb-src in /etc/apt/sources.list > and run : > > apt-get build-dep sernet-samba > apt-get source sernet-samba -b > > you wil end up with .deb files ;-) yep, thanks - I'll check it

...en); + vlen = getxattr (src, names[i], attrval, vlen); CHROOT_OUT; if (vlen == -1) { - reply_with_perror ("getxattr: %s, %s", src, &buf[i]); + reply_with_perror ("getxattr: %s, %s", src, names[i]); goto error; } CHROOT_IN; - ret = setxattr (dest, &buf[i], attrval, vlen, 0); + ret = setxattr (dest, names[i], attrval, vlen, 0); CHROOT_OUT; if (ret == -1) { - reply_with_perror ("setxattr: %s, %s", dest, &buf[i]); + reply_with_perror ("setxattr: %s, %s", dest, names[i]); goto erro...

...en); + vlen = getxattr (src, names[i], attrval, vlen); CHROOT_OUT; if (vlen == -1) { - reply_with_perror ("getxattr: %s, %s", src, &buf[i]); + reply_with_perror ("getxattr: %s, %s", src, names[i]); goto error; } CHROOT_IN; - ret = setxattr (dest, &buf[i], attrval, vlen, 0); + ret = setxattr (dest, names[i], attrval, vlen, 0); CHROOT_OUT; if (ret == -1) { - reply_with_perror ("setxattr: %s, %s", dest, &buf[i]); + reply_with_perror ("setxattr: %s, %s", dest, names[i]); goto erro...

...0.001896 0 250052 _llseek > 0.28 0.001849 0 170052 mmap2 > 0.25 0.001682 0 340100 rt_sigaction > 0.18 0.001208 0 200097 fstat64 > 0.13 0.000878 0 25001 setxattr > 0.09 0.000602 0 15000 SYS_320 > 0.03 0.000227 0 30000 20000 flock > 0.03 0.000194 0 5000 ftruncate64 > 0.01 0.000067 0 6110 fstatat64 > 0.01 0.000050 0...

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 # file:

...t; touch uses the 0666 create mode, the exec bit is not set. So far so good. > > Now to samba. The share has these controls: > > ... > create mask = 0664 > ... > > When stracing the samba process, I see that 0664 is specified in the open > system call, but following that, setxattr is called (not sure by samba or > some kernel process), which must be setting the exec bit on the group? > > ... > 96012 open("new", O_RDWR|O_CREAT|O_EXCL, 0664) = 40 > 96012 setxattr("New Text Document.txt", "system.posix_acl_access", > LONG_HEX_STRI...

Hi, >From strace, I can see the system calls setxattr and getxattr. Two things I don't understand is: 1. how does the file got created so quickly, from where it read the stats. 2.why is the added attribute missing if I check with getfattr? Regards, Jeevan. On Nov 13, 2017 12:40 PM, "Amar Tumballi" <atumball at redhat.com> wr...

...tgroups32 0.28 0.001896 0 250052 _llseek 0.28 0.001849 0 170052 mmap2 0.25 0.001682 0 340100 rt_sigaction 0.18 0.001208 0 200097 fstat64 0.13 0.000878 0 25001 setxattr 0.09 0.000602 0 15000 SYS_320 0.03 0.000227 0 30000 20000 flock 0.03 0.000194 0 5000 ftruncate64 0.01 0.000067 0 6110 fstatat64 0.01 0.000050 0 850 850 connect...

...r *link = cookie; + + kfree(link); } const struct inode_operations ocfs2_symlink_inode_operations = { .readlink = page_readlink, - .follow_link = ocfs2_follow_link, + .follow_link = page_follow_link_light, + .put_link = page_put_link, .getattr = ocfs2_getattr, .setattr = ocfs2_setattr, .setxattr = generic_setxattr, @@ -171,7 +167,8 @@ const struct inode_operations ocfs2_symlink_inode_operations = { }; const struct inode_operations ocfs2_fast_symlink_inode_operations = { .readlink = ocfs2_readlink, - .follow_link = ocfs2_follow_link, + .follow_link = ocfs2_fast_follow_link, + .put_link...

Hi Jones, many thanks for your reply. Yepp, I'm using ACL's (Posix ACL's) on filesystem to regulate the access of users for files and directories. Do you mean that this is the "normal" way? These geteuid and getegid system calls are so slow? On the previous system (Debian Wheezy, Samba 3) I've also used ACL's, but there were much faster than this... What should

...ftruncate64 0.33 0.001595 0 160039 mmap2 0.27 0.001287 0 80020 read 0.20 0.000963 0 190058 fstat64 0.17 0.000814 0 160040 _llseek 0.16 0.000786 0 25001 setxattr 0.09 0.000423 0 15000 SYS_320 0.05 0.000220 4 54 getdents64 0.04 0.000214 0 30004 clock_gettime 0.01 0.000038 0 800 800 connect 0.01 0.000032 0 5000 flo...

v1 here: https://www.redhat.com/archives/libguestfs/2020-March/msg00099.html This one fixes most of the points picked up in review, and does not strdup the strings which should keep down memory usage if that is a concern. Rich.