strib
commented
5 years ago Looks like you have a ton of "conflicting" data in your local private folder for some reason. There's no much of it (about 13 GB) that while it's trying to load it into memory, it's blocking other operations and timing them out.
Obviously this is a bug on our end. You get into "conflict" when two devices try to write to the same folder at the same time. One of them wins, and the other one has to re-do their writes. Usually this happens automatically in the background, but it seems like when you were on an older version of Keybase you were hitting a crasher while trying to do this (which has now been fixed). While in conflict mode, you just kept accumulating more data in conflict mode, leading to the current mess.
This is relatively easy to workaround, if you haven't written any data to your private folder from that device that you can't recover from other copies. (You can probably figure out what data will be lost by viewing the folder from a different device and seeing what's missing.) If that's the case, you can:
- Stop Keybase completely, so that the file system mount goes away.
- Run this command from a terminal:
mv "$HOME/Library/Application Support/Keybase/kbfs_journal/v1/01206b9477bf7655c668feffb2f609b394ab-5056d7eaf4ab6f49" "$HOME/Library/Application Support/Keybase/kbfs_journal/v1/5056d7eaf4ab6f49.bkp" - Relaunch Keybase
At that point, your private folder should be openable and will appear like it does from the other devices.
And when you're sure you haven't lost any data, you can nuke that .bkp directory you just made, to reclaim the 13GB.
Sorry for the bad experience, let me know how it goes, or if you need help recovering any data from that device.
ghost
The kbfs file system is no longer accessible in both the Keybase app and in the Finder (I'm using OS X 10.14.2). Errors in app are: Failed to list folder, Failed to load file metadata. Tried reinstalling keybase. Is there any way to reset/wipe the kbfs and start over?
My log id: acb0289e47f2e427fa75841c