Hi,
Thanks. Now I understand :)
On Nov 13, 2017 1:06 PM, "Krutika Dhananjay" 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
On Mon, Nov 13, 2017 at 12:14 PM, Jeevan Patnaik
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
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
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