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

Unimplemented opcode OPCODE-52 (STATX) #819

Open
daniel156161 opened this issue Jan 20, 2024 · 4 comments
Open

Unimplemented opcode OPCODE-52 (STATX) #819

daniel156161 opened this issue Jan 20, 2024 · 4 comments

Comments

@daniel156161
Copy link

When mouting a encrypted directory i am getting Unimplemented opcode OPCODE-52

do i must get worry of my data?

Decrypting master key
21:54:51.936000 Unimplemented opcode OPCODE-52
Filesystem mounted and ready.
@rfjakob
Copy link
Owner

rfjakob commented Jan 23, 2024

Huh, what Linux version is this (uname -a)? Linux is sending a command that gocryptfs does not understand. But not, this should not affect normal operation.

@daniel156161
Copy link
Author

my linux version is
Linux framework 6.6.10-1-MANJARO #1 SMP PREEMPT_DYNAMIC Fri Jan 5 17:38:36 UTC 2024 x86_64 GNU/Linux

@dmarto
Copy link

dmarto commented Jan 25, 2024

Purely coincidentally, while looking for something else earlier, I came across this issue. Now, I've noticed that I have it too.

Just to be fully transparent, I'm not running the latest gocryptfs; I'm on v2.3.2. I observed the issue while running fsck on a backup (haven't checked on mount). I'm not particularly concerned about it, but I thought I'd chime in.

Linux [..] 6.7.1_1 #1 SMP PREEMPT_DYNAMIC Sat Jan 20 19:48:38 UTC 2024 x86_64 GNU/Linux

@SimonPilkington
Copy link

I assume it's statx from here: https://elixir.bootlin.com/linux/latest/source/include/uapi/linux/fuse.h#L621

Implemented in fuse somewhat recently and falls back to old behaviour if not implemented so nothing to worry about.

@rfjakob rfjakob changed the title Unimplemented opcode OPCODE-52 Unimplemented opcode OPCODE-52 (STATX) Apr 18, 2024
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

4 participants