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

Problem with FUSE and OneNote. #2288

Open
2 tasks done
bvazx opened this issue Jun 9, 2022 · 10 comments
Open
2 tasks done

Problem with FUSE and OneNote. #2288

bvazx opened this issue Jun 9, 2022 · 10 comments
Labels
mount:fuse os:windows state:confirmed We are able to reproduce the reported behavior type:bug Something isn't working

Comments

@bvazx
Copy link

bvazx commented Jun 9, 2022

Please agree to the following

Summary

When I use FUSE, OneNote is closed for no reason.

What software is involved?

  • Operating System: Windows 11 Pro
  • Cryptomator: 1.6.10
  • Microsoft 365: OneNote

Volume Type

FUSE

Steps to Reproduce

  1. Create a new notebook for OneNote in the virtual drive (vault).
  2. Work in the created notebook.

Expected Behavior

OneNote should not close.

Actual Behavior

After a certain time, OneNote is closed for no reason.
I think it happens when recording to the virtual drive (vault).
When I use Dokany 1.5.1 or WebDAV, it doesn’t happen.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@bvazx bvazx added the type:bug Something isn't working label Jun 9, 2022
@infeo infeo added state:confirmed We are able to reproduce the reported behavior mount:fuse os:windows labels Jun 13, 2022
@infeo
Copy link
Member

infeo commented Jun 13, 2022

Does also happen on Windows 10. Using the bare voulme provider library fuse-nio-adapter, the log is
fuseNio_crypto.log

Of interest are lines 407 ff where it is tried to release a non existing file.

@bvazx
Copy link
Author

bvazx commented Oct 8, 2022

Oh, when will you correct this bug?

@overheadhunter
Copy link
Member

Of interest are lines 407 ff where it is tried to release a non existing file.

11:14:21.236 [Thread-342] TRACE org.cryptomator.frontend.fuse.OpenFileFactory - Opening 2 OpenFile{path=/wakulu.one, channel=org.cryptomator.cryptofs.ch.CleartextFileChannel@17e8a6b6}
11:14:21.236 [Thread-343] TRACE org.cryptomator.frontend.fuse.ReadWriteAdapter - unlink /wakulu.one
11:14:21.236 [Thread-344] TRACE org.cryptomator.frontend.fuse.ReadOnlyAdapter - release /wakulu.one (2)
11:14:21.236 [Thread-344] TRACE org.cryptomator.frontend.fuse.OpenFileFactory - Releasing 2 OpenFile{path=/wakulu.one, channel=org.cryptomator.cryptofs.ch.CleartextFileChannel@17e8a6b6}
11:14:21.236 [Thread-344] ERROR org.cryptomator.frontend.fuse.ReadOnlyAdapter - release /wakulu.one failed.
java.nio.file.NoSuchFileException: T:\vaultFormat8\d\TY\OIE623ER622PE7JKBJYNYDQ4XPUTEV\46WB71BHtS3Pu6BpmSg2ennKj4-Goebtcvg=.c9r
	at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:85)
	at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
	at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
	at java.base/sun.nio.fs.WindowsFileAttributeViews$Basic.setFileTimes(WindowsFileAttributeViews.java:91)
	at java.base/sun.nio.fs.WindowsFileAttributeViews$Basic.setTimes(WindowsFileAttributeViews.java:149)
	at org.cryptomator.cryptofs.ch.CleartextFileChannel.persistLastModified(CleartextFileChannel.java:246)
	at org.cryptomator.cryptofs.ch.CleartextFileChannel.implCloseChannel(CleartextFileChannel.java:314)
	at java.base/java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:112)
	at org.cryptomator.frontend.fuse.OpenFile.close(OpenFile.java:103)
	at org.cryptomator.frontend.fuse.OpenFileFactory.close(OpenFileFactory.java:78)
	at org.cryptomator.frontend.fuse.ReadOnlyFileHandler.release(ReadOnlyFileHandler.java:81)
	at org.cryptomator.frontend.fuse.ReadOnlyAdapter.release(ReadOnlyAdapter.java:247)
	at ru.serce.jnrfuse.AbstractFuseFS.lambda$init$7(AbstractFuseFS.java:150)
	at jnr.ffi.provider.jffi.NativeClosureProxy$$impl$$14.invoke(Unknown Source)

I guess unlinking should fail, if the file is still opened. But the behaviour may depend on the OS... Didn't find any docs yet.

@bvazx
Copy link
Author

bvazx commented Mar 1, 2023

I test version 1.7.0. This bug does not appear until...

@bvazx
Copy link
Author

bvazx commented Mar 1, 2023

I launched the optimization of notebooks. Was successful. Earlier because of this bug, OneNote flew out...

@infeo
Copy link
Member

infeo commented Mar 1, 2023

@bvazx Is this bug fixed or not with 1.7.0 ?

@bvazx
Copy link
Author

bvazx commented Mar 1, 2023

Unfortunately present...
Easy to check.
Create a new notebook in the vault, open a new page in it... And that's it...
With Dokany 1.5.1 or WebDAV everything is okey!

@bvazx
Copy link
Author

bvazx commented Mar 11, 2023

I also want to pay attention to this.
When I used version 1.7.0 - 1.7.2 and Dokany 1.5.1, these versions of Cryptomator constantly turned to the vault, loaded the processor.
And also, I could not close the vault due to the fact that supposedly some files were busy... Only through the tasksmanager.
I had to return to version 1.6.17.

@bvazx
Copy link
Author

bvazx commented Mar 19, 2023

I installed version 1.7.2. I chose as a volume for mounting "WinFsp (Local Drive)".
I test OneNote. Where OneNote used to fly out with an error, while it works...
I will watch. I'll write.

@bvazx
Copy link
Author

bvazx commented Mar 19, 2023

OneNote is crashed. The Bug is present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mount:fuse os:windows state:confirmed We are able to reproduce the reported behavior type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants