Hi, Thanks. Now I understand :)
On Nov 13, 2017 1:06 PM, "Krutika Dhananjay" <[email protected]> wrote: > trusted.io-stats-dump is a virtual (not physical) extended attribute. > The code is written in a way that a request to set trusted.io-stats-dump > gets bypassed at the io-stats translator layer on the stack and > there it gets converted into the action of dumping the statistics into the > provided output file path. > See io_stats_setxattr() implementation in io-stats.c for more details. > > HTH, > Krutika > > On Mon, Nov 13, 2017 at 12:14 PM, Jeevan Patnaik <[email protected]> > wrote: > >> 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: mnt/gluster/gv0_glusterfs >> trusted.glusterfs.dht.commithash="3480667945 <03480%20667%20945>" >> >> Regards, >> Jeevan. >> >> _______________________________________________ >> Gluster-users mailing list >> [email protected] >> http://lists.gluster.org/mailman/listinfo/gluster-users >> > >
_______________________________________________ Gluster-users mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-users
