[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Ivan Čukić changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Bharadwaj Raju changed: What|Removed |Added Resolution|UPSTREAM|--- Ever confirmed|0 |1 CC||bharadwaj.raju777@protonmai ||l.com Status|RESOLVED|REOPENED --- Comment #11 from Bharadwaj Raju --- As the cryfs report notes, this problem can be mitigated by choosing a larger block size by default. Assuming it works, it sounds like a good solution we can implement in KDE. Reopening. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #10 from Ken --- (In reply to Ivan Čukić from comment #8) > @Ken > > You should try from the terminal - when dolphin/krusader get blocked, test > whether you can open some file in vim or another console editor. If that > works, then you might be experiencing an issue that *is* somewhere in KDE (I > assume krusader uses the same underlying libraries as dolpgin, though I > might be mistaken) @Ivan - will do. Thanks for the suggestion. @Zvi - apologies for muddying the waters on your ticket. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #9 from Zvi Baratz --- Reported in cryfs. Link for future reference: https://github.com/cryfs/cryfs/issues/346 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #8 from Ivan Čukić --- @Ken You should try from the terminal - when dolphin/krusader get blocked, test whether you can open some file in vim or another console editor. If that works, then you might be experiencing an issue that *is* somewhere in KDE (I assume krusader uses the same underlying libraries as dolpgin, though I might be mistaken) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #7 from Ken --- (In reply to Ivan Čukić from comment #4) > @Ken > > You can open a separate bug report on Dolphin. > > Dolphin is not to blame for "Filesystem is not responding" reported by Zvi. > There have been reports here of cryfs being blocked even in terminal. So, > nothing to do with Dolphin. Looks like you're correct about it not being Dolphin. Hang issue is still present using Krusader as well. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #6 from Ivan Čukić --- @Zvi Yes, please :) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #5 from Zvi Baratz --- @Ivan I can confirm after switching to Veracrypt I had no problem using Dolphin, so the problem indeed does not seem to be related to it. Just to make sure I understood correctly - I should open an issue in cryfs (https://github.com/cryfs/cryfs)? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #4 from Ivan Čukić --- @Ken You can open a separate bug report on Dolphin. Dolphin is not to blame for "Filesystem is not responding" reported by Zvi. There have been reports here of cryfs being blocked even in terminal. So, nothing to do with Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #3 from Ken --- Cryfs is not the issue. The issue is dolphin and any large ecrypted filesystem. I get similar behavior with veracrypt volumes mounted using zulucrypt. Dolphin has consistently takes a dive anytime a new filesystem device is suddenly mounted with hundreds of thousands of files. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Ivan Čukić --- Hi all, This is something that needs to be reported upstream. It would be great if you have the time to do so and provide the cryfs authors with feedback / more information they might need. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Ken changed: What|Removed |Added CC||k...@macferrin.com --- Comment #1 from Ken --- Exact same issue. Kubuntu 20.04. Large cryfs (100GB+) become unresponsive for several minutes after mounting. Causes dolphin to freeze for long periods. -- You are receiving this mail because: You are watching all bug changes.
