You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After inode 1 for the root fs node I set starting inode number at 100 and increment it with every created node.
I use the ino field in the stat struct.
When doing a stat on any of my fuse nodes I can see the count starts from 1 and does not jump to 100+.
const fuse = new Fuse('./mnt', ops, {
debug: false,
displayFolder: false,
autoUnmount: true,
force: true,
kernelCache: false,
useIno: true // <- this does not appear to be used
});
Looking at _fuseOptions in index.js I can see that use_ino is not something that is pushed into the -o option returned from the function for the fuse mount options.
The text was updated successfully, but these errors were encountered:
paulrobello
changed the title
[Question] useIno option does not appear to use custom ino values in stat struct
[BUG] useIno option does not appear to use custom ino values in stat struct
Feb 28, 2021
After inode 1 for the root fs node I set starting inode number at 100 and increment it with every created node.
I use the ino field in the stat struct.
When doing a stat on any of my fuse nodes I can see the count starts from 1 and does not jump to 100+.
const fuse = new Fuse('./mnt', ops, {
debug: false,
displayFolder: false,
autoUnmount: true,
force: true,
kernelCache: false,
useIno: true // <- this does not appear to be used
});
Looking at _fuseOptions in index.js I can see that use_ino is not something that is pushed into the -o option returned from the function for the fuse mount options.
Added option in PR33
The text was updated successfully, but these errors were encountered: