I don't think the problem is with the handling of SETATTR in either NetBSD or Linux. I am guessing NetBSD FUSE is _using_ SETATTR to update atime upon open? Linux FUSE just leaves it to the backend filesystem to update atime. Whenever there is a SETATTR fop, ctime is _always_ bumped.<br><div><br></div><div>Thanks</div><br><div class="gmail_quote">On Mon Jan 12 2015 at 5:03:51 PM Emmanuel Dreyfus <<a href="mailto:manu@netbsd.org">manu@netbsd.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello<br>
<br>
Here is a NetBSD behavior that looks pathological:<br>
(it happens on a FUSE mount but not a native mount):<br>
<br>
# touch a<br>
# stat -x a<br>
File: "a"<br>
Size: 0 FileType: Regular File<br>
Mode: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/<br>
wheel)<br>
Device: 203,7 Inode: 13726586830943880794 Links: 1<br>
Access: Tue Jan 13 01:57:25 2015<br>
Modify: Tue Jan 13 01:57:25 2015<br>
Change: Tue Jan 13 01:57:25 2015<br>
# cat a > /dev/null<br>
# stat -x a<br>
File: "a"<br>
Size: 0 FileType: Regular File<br>
Mode: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/<br>
wheel)<br>
Device: 203,7 Inode: 13726586830943880794 Links: 1<br>
Access: Tue Jan 13 01:57:31 2015<br>
Modify: Tue Jan 13 01:57:25 2015<br>
Change: Tue Jan 13 01:57:31 2015<br>
<br>
NetBSD FUSE implementation does not sends ctime with SETATTR. Looking at<br>
glusterfs FUSE xlator, I see setattr code does not handle ctime either.<br>
<br>
How does that happen? What wrong does NetBSD SETATTR does?<br>
<br>
--<br>
Emmanuel Dreyfus<br>
<a>http://hcpnet.free.fr/pubz</a><br>
<a>manu@netbsd.org</a><br>
______________________________<u></u>_________________<br>
Gluster-devel mailing list<br>
<a>Gluster-devel@gluster.org</a><br>
<a>http://www.gluster.org/<u></u>mailman/listinfo/gluster-devel</a><br>
</blockquote></div>