<br><br><div class="gmail_quote">On Mon, Feb 11, 2013 at 4:15 AM, Raghavendra Bhat <span dir="ltr"><<a href="mailto:rabhat@redhat.com" target="_blank">rabhat@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<br>
I have found out this behavior when open-behind is enabled.<br>
<br>
Suppose 2 fuse clients are mounted. Create a file with some data. open the file, sleep for some time, (while sleeping remove the file opened from other client), read from the opened fd. Actually since the file open was successful and fd is there, read operation should be successful. But with open-behind even though open is successful, read is failing and getting EUCLEAN (structure needs cleaning).<br>
<br>
When open-behind is turned off, then even though the file is deleted from other mount point after being opened, the process is able to read the file.<br>
<br></blockquote><div><br></div><div>This is not an issue introduced with the open-behind refactor. This behavior has always existed even in the previous quick-read xlator.</div><div><br></div><div>Avati</div></div>