direct_io support about go-fuse HOT 7 CLOSED

have you tried adding the "direct_io" option to mount, https://godoc.org/github.com/hanwen/go-fuse/fuse#MountOptions?

from go-fuse.

Hi @hanwen

I tried direct_io option, but cannot figure out why it doesn't work on my setup(Ubuntu 16.04):

conn := nodefs.NewFileSystemConnector(newFs.Root(), nil)
opts := &fuse.MountOptions{
                        MaxBackground: 12,
                        Options:       []string{"direct_io"},
                }
server, err := fuse.NewServer(conn.RawFS(), fs.GetMountDir(), opts)

fusermount reports:

/bin/fusermount: mount failed: Invalid argument

And if I remove direct_io option it works.

from go-fuse.

try

func(fs *FS) Open(name string, flags uint32, context *fuse.Context) (nodefs.File, fuse.Status) {
        f := ...
        return &nodefs.WithFlags{
                File:      f,  
                FuseFlags: fuse.FOPEN_DIRECT_IO,
        }, fuse.OK
}

from go-fuse.

Thanks @vChrysanthemum , I've figured that out lately, but it still doesn't work for me. I am sure kernel is handling the file in direct-io mode but it somehow hangs(soft lock up) due to waiting for a page to be locked. I am still investigating.

And I saw bazil/fuse seems tested with direct_io already, so may want to give that a try as well.

from go-fuse.

Just a update: soft lock up caused by a kernel bug in FUSE interaction with loopback device. It exists after Linux v4.1. Details can be found at https://sourceforge.net/p/fuse/mailman/message/35276378/

from go-fuse.

having the same issue , can not support when using namazu with direct_io , it use this go-fuse lib.
@yasker
have you find out how to support this direct_io?

from go-fuse.

you can use directio by specifying the fuse.FOPEN_DIRECTIO flag from create or open methods.

from go-fuse.