Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster, 2017-12-30

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:07 Vapez joined #gluster
00:27 ic0n joined #gluster
00:38 rouven joined #gluster
01:10 ic0n joined #gluster
01:30 ic0n joined #gluster
01:32 brettnem_ joined #gluster
01:50 ic0n joined #gluster
01:57 nh2[m] joined #gluster
01:58 nh2[m] hi, my CHANGELOG.* files are full of `SETATTR` and `REMOVEXATTR` (in turn), a couple per second.
01:58 nh2[m] how can I find out what creates those? I can't seem to find a program on my machines that does those syscalls on my gluster fuse mount
02:28 ic0n joined #gluster
02:35 nh2[m] OK, it seems to be my application doing `getxattr()` and `llistxattr()` calls, but aren't those read-only? How can they turn into `SETATTR` FOPs?
02:59 ilbot3 joined #gluster
02:59 Topic for #gluster is now Gluster Community - https://www.gluster.org | Documentation - https://gluster.readthedocs.io/en/latest/ | Patches - https://review.gluster.org/ | Developers go to #gluster-dev | Channel Logs - https://botbot.me/freenode/gluster/ & http://irclog.perlgeek.de/gluster/
03:02 adon joined #gluster
03:07 ic0n joined #gluster
03:51 ic0n joined #gluster
04:04 Rakkin_ joined #gluster
04:26 plarsen joined #gluster
04:35 msvbhat joined #gluster
04:46 ic0n joined #gluster
05:00 ic0n joined #gluster
05:12 krk joined #gluster
05:22 msvbhat joined #gluster
05:30 nbalacha joined #gluster
05:38 ic0n joined #gluster
05:52 ic0n joined #gluster
05:58 Rakkin_ joined #gluster
06:07 ic0n joined #gluster
06:09 arif-ali joined #gluster
06:23 ic0n joined #gluster
06:29 mlg9000 joined #gluster
06:40 mlg9000 joined #gluster
06:47 ic0n joined #gluster
07:10 gyadav joined #gluster
07:16 ic0n joined #gluster
07:32 drymek joined #gluster
07:42 major joined #gluster
07:42 drymek joined #gluster
07:52 msvbhat joined #gluster
07:52 ic0n joined #gluster
08:15 major joined #gluster
08:24 ic0n joined #gluster
09:37 psony joined #gluster
10:03 major joined #gluster
10:36 zcalusic left #gluster
11:48 ic0n joined #gluster
12:13 MrAbaddon joined #gluster
12:33 rouven joined #gluster
12:41 illwieckz joined #gluster
13:09 atinm_ joined #gluster
13:31 ic0n joined #gluster
13:46 Vapez joined #gluster
13:51 illwieckz joined #gluster
14:15 illwieckz joined #gluster
14:23 ic0n joined #gluster
14:54 ic0n joined #gluster
15:20 major joined #gluster
15:40 ic0n joined #gluster
16:22 ic0n joined #gluster
17:05 ic0n joined #gluster
17:20 ic0n joined #gluster
17:49 ic0n joined #gluster
17:52 arpu joined #gluster
17:54 gyadav joined #gluster
18:18 ic0n joined #gluster
18:22 JoeJulian nh2[m]: Gluster itself uses ,,(extended attributes) for metadata.
18:22 glusterbot nh2 [m] : (#1) To read the extended attributes on the server: getfattr -m .  -d -e hex {filename}, or (#2) For more information on how GlusterFS uses extended attributes, see this article: http://pl.atyp.us/hekafs.org/index.php/2011/04/glusterfs-extended-attributes/
18:23 nh2[m] JoeJulian: right, but that is on the brick FS. As far as I can tell, if you do `listxattr()` on the *mount*, that should be a read-only operation
18:31 Rakkin_ joined #gluster
18:41 sanoj joined #gluster
18:43 JoeJulian Many of the translators that make use of xattr metadata happen on the client.
18:43 ic0n joined #gluster
19:07 jkroon joined #gluster
19:07 ic0n joined #gluster
19:33 ahino joined #gluster
19:38 ic0n joined #gluster
19:46 bwerthmann joined #gluster
19:51 bwerthma1n joined #gluster
19:58 ic0n joined #gluster
20:13 plarsen joined #gluster
20:40 ic0n joined #gluster
20:55 ic0n joined #gluster
21:09 Vapez joined #gluster
21:15 ic0n joined #gluster
21:43 kettlewell joined #gluster
21:57 rouven joined #gluster
22:03 ic0n joined #gluster
22:37 ic0n joined #gluster
22:44 brettnem joined #gluster
22:52 ic0n joined #gluster
23:30 ic0n joined #gluster

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary