From: Goswin v. B. <gos...@we...> - 2009-07-20 11:25:50
|
Csaba Henk <csa...@cr...> writes: > On 2009-07-10, Bastien Bouzerau <meg...@gm...> wrote: >> I'm actually working on a nfs-based caching filesystem. This file system >> uses fuse and is implemented in python. My fusermount version is 2.7.4. To >> obtain best performances with my filesystem I would like to use the fuseblk >> mount type. I didn't find how to set this fuse_attr by *fuse*-*python* API. >> Of course, if I put blksize option with FuseOptParse, the answer is blksize >> unknown option. >> I always have type fuse when mounting. >> If I make cat /proc/filesystems, I can see fuseblk device. >> So if you have any idea, it would be very nice to help me. > > In general (not just in the Python binding), you need to pass the > "-oblkdev" option to libfuse's appropriate filesystem initialization routine. > > In Python, if your fs processes command line options via the "parse" method of > the Fuse class, then you can use "-oblkdev" in the command line, and it > will be passed down to the library code and it takes effect. > > Although I guess you'd prefer it being set it internally. You can add it > in between parse() and main() [given that you use parse()... I don't > know a reason for not using it, so let me assume it :) ], somehow like this: > > fs.parse() > fs.fuse_args.add("blkdev") > fs.main() > > Csaba Don't you also have to specify the device to use? MfG Goswin |