Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fuse: unknown option(s): `-o use_ino,nonempty' #141

Open
multiple1 opened this issue Feb 7, 2024 · 2 comments
Open

fuse: unknown option(s): `-o use_ino,nonempty' #141

multiple1 opened this issue Feb 7, 2024 · 2 comments

Comments

@multiple1
Copy link

multiple1 commented Feb 7, 2024

Hello!
I am using the same mount options as in the example: https://github.com/rpodgorny/unionfs-fuse/blob/master/examples/S01a-unionfs-live-cd.sh#L6C42-L6C43

But I get this error using libfuse3.16.2:

fuse: unknown option(s): `-o use_ino,nonempty'

It seems that libfuse does no longer allow the use_ino mount option, because it should be set by the filesystem and not by the user.
libfuse/libfuse@8ee553d

So am I safe to simply remove use_ino and unionfs-fuse handles this correctly?
I could not find use_ino in the unionfs source code, so I am not sure!

@bsbernd
Copy link
Contributor

bsbernd commented May 7, 2024

Sorry for late reply, I'm super busy. use_ino basically enables using the inode number provided by struct stat, instead of using a fuse internal consecutive counter. I think I had added that option to the examples/man-page as it helps to verify the right branch is used for a file. In the end neither fuse-internal inode number nor underlying file system inode (use_ino) are correct, as the inode number should be conserved during copy-on-write. And inode numbers also should be unique across different branches - for that the fuse internal inode number is even a little better.

@rpodgorny
Copy link
Owner

yeah, i've removed mentions of "use_ino" from examples and documentation. will be in next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants