That's as designed. If the inode number changes, you *will* get an
EIO. It is a "real" file system after all, so you can stretch the
rules only so much.

Amit

On Jun 26, 9:30 pm, "Amar (ಅಮರ್ ತುಂಬಳ್ಳಿ)" <[EMAIL PROTECTED]> wrote:
> one more question. i got a EIO when the inode number of the file changed
> while doing 'ls -l' (may be other client deleted the file and created it
> again). EIO was surely generated inside MacFUSE (as filesystem itself didn't
> had any errors, other than a warning of inode number changed). Is it also
> related to not updating the stat in lookup to newer values?
>
> Regards,
> Amar
>
> 2008/6/26 Amit Singh <[EMAIL PROTECTED]>:
>
>
>
> > That's a bug. After the attribute timeout (default 1s), it should show
> > the new size. I broke it at some point--sorry about that. I'll fix it
> > in the tree and it should be in the next release.
>
> --
> Amar Tumballi
> Gluster/GlusterFS Hacker
> [bulde on #gluster/irc.gnu.org]http://www.zresearch.com- Commoditizing Super 
> Storage!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"macfuse-devel" group.
To post to this group, send email to macfuse-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/macfuse-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to