fuse-devel

[fuse-devel] Low Level Api support for mmap and lssek

[Jojy V. <joj...@gm...>]

Hi All
  I am a relatively new use of  Fuse and am trying to implement lseek and
mmap for the files to be hosted by the fuse file system. I dont see any low
level operation called lseek or mmap and so was wondering if this is
possible.  In the kernel, these operations belong to the file operations and
I was hoping to get the same functionality using fuse.

thanks again
Jojy G Varghese

Re: [fuse-devel] Low Level Api support for mmap and lssek

[Goswin v. B. <gos...@we...>]

Jojy Varghese <joj...@gm...> writes:

> Hi All
>   I am a relatively new use of  Fuse and am trying to implement lseek and
> mmap for the files to be hosted by the fuse file system. I dont see any low
> level operation called lseek or mmap and so was wondering if this is
> possible.  In the kernel, these operations belong to the file operations and
> I was hoping to get the same functionality using fuse.
>
> thanks again
> Jojy G Varghese

lseek() just updates the file offset in the applications file
descriptor. That has no effect on the filesystem.

As for mmap afaik the only thing you see of that is read()/write()
callbaks of page sized chunks. There isn't any difference (for your
filesystem) between a read/write due to mmap or due to read/write
calls.

MfG
        Goswin

[fuse-devel] Transport endpoint is not connected

[Dave W. <Dav...@Re...>]

I'm using ciopfs which uses fuse
however I get this error when it's up and running [usually under heavy load]
I'm running on BlueWhite64 - [64bit slackware clone] - not he latest version but I'm using 
the latest ciopfs and fuse 2.8.1

when I run ciopfs as -s that error goes away but I'm left with 
ulockmgr_server: open file descriptors on exit
after a while of running,

has anyone got any ideas on how I can fix this or what the problem really is ?

Dave
-- dazed and confused