[Gluster-devel] how does meta xlator work?

[Emmanuel Dreyfus]

Anand Avati <avati at gluster.org> wrote:

> In meta all file sizes are 0 (since the contents of the inode are generated
> dynamically on open()/read(), size is unknown during lookup() -- just like
> /proc). And therefore all meta file open()s are forced into direct_io_mode (
> http://review.gluster.org/7506) so that read() requests are sent straight
> to FUSE/glusterfs bypassing VFS (size is ignored etc.)

I found the code in the kernel that skips the read if it is beyond known
file size. Hence I guess the idea is that on lookup of a file with a
size equal to 0, a special handling should be done so that reads happens
anyway.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org