From: Bobi33 <bob...@ya...> - 2012-02-17 10:20:45
|
Hi All, I enabled the big_writes option for my fuse client implementation and whenever I have a write request I also get a getxattr call. Do you have any idea of why this happens? When not enabling the big writes option everything works fine (no extra getxattr call). You can imagine that the performance of write requests is strongly affected by this. If I remove the getxattr callback it all work fine, but I need the extended attributes in the future so this is not an option. I looked over the fuse source code but I couldn't figure it out where the problem might be. I am using: fuse-libs-2.8.3-4.el6.x86_64 fuse-devel-2.8.3-4.el6.x86_64 gvfs-fuse-1.4.3-12.el6.x86_64 fuse-2.8.3-4.el6.x86_64 Thanks in advance. -- View this message in context: http://old.nabble.com/Big-writes-option-and-getxattr-tp33341708p33341708.html Sent from the Fuse - Dev mailing list archive at Nabble.com. |
From: Miklos S. <mi...@sz...> - 2012-03-05 16:26:31
|
Bobi33 <bob...@ya...> writes: > Hi All, > > I enabled the big_writes option for my fuse client implementation and > whenever I have a write request I also get a getxattr call. > Do you have any idea of why this happens? When not enabling the big writes > option everything works fine (no extra getxattr call). Strange. Can you send a log (enabled with -d) with and without the bigwrites option? Thanks, Miklos |