kbfs failures
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
I tried rsyncing ~85GB dir to kbfs. I got error: rsync: write failed on : Transport endpoint is not connected (107)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]
Now /keybase has KBFS_NOT_RUNNING link and there is no way to start kbfs again. run_keybase returns: Job for kbfs.service failed because a timeout was exceeded.
~/.local/share/keybase has grown to ~60GB.
This happens second time. Deleting ~/.local/share/keybase allows to restart service but deletion of this folder is painfully slow as it contains tons of small files.
my log id: cb6789a950feafae0003eb1c
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the supplied log id cb6789a950feafae0003eb1c and the reported rsync failure, then investigate why the KBFS service times out after the transport endpoint disconnects. The issue is resolved when KBFS can restart without requiring deletion of ~/.local/share/keybase and the large-directory sync no longer leaves KBFS_NOT_RUNNING.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100