kbfs seems to be melting down for git and private file access.

[l1a]

I seem to be melting down on all devices/clients (linux fedora 31 and macos catalina).

GUI shows "An unexplainable error has occurred." when accessing the below.

git repos are all giving me: "git-remote-keybase error: (1) Server: block does not exist".

/keybase/private/kentobias access is giving me: "/keybase/private/kentobias": Input/output error (os error 5)" from all devices.

/keybase/private/kentobias,someuser seems OK.

/keybase/public/path seems OK.

my log id: ec601d0ffead8dbeb12c3a1c

[l1a]

Well, that lasted for about 12 hrs. Now all is right with the world. I changed nothing and rebooted/restarted nothing between when it was broken everywhere and now when it's fine.

[strib]

@l1a thanks for the report. I know it's working now, but I looked into it a bit and it seems like your device durin-nuc-01 uploaded an update incompletely around 9:10 am Pacific time this morning, and only completed the write around 1:06 pm Pacific time this afternoon. In between those times, other clients would have seen those errors (and perhaps there was another discrepancy before that time period, since you said it lasted 12 hours, not just 4).

But it shouldn't be possible for these incomplete writes to happen. Could you please do a keybase log send from your device durin-nuc-01 and report the log ID here so I can take a look to see why the upload to our servers was incomplete for so long (or at all)? I'm especially curious to see what version of Keybase you're running on that device, since for some reasons our servers can't identify it. Thanks!

[l1a]

327cc0ad27eb50b3f8e12f1c is durin-nuc-01 log send.

12 was an estimate. But this did start sometime last night. durin-nuc-01 was attempting to upload a big file (~750M) and seemed to hang. Worth noting that the device is fedora 31 server. Has 8G mem and 8G swap. Both were maxed by keybase (can't recall if it was kbfs or not) as well as 100% CPU. In the morning the mem use was down to about 1/2 that. Did an os update (including kernel but keybase was up to date) and reboot. keybase was working hard after for hours but not with so much CPU or memory use.

[strib]

Thanks! I do see some issues (probable bugs) in those logs, but unfortunately the limited portion sent by keybase log send doesn't go back far enough to see the source of the problem. If you're willing to share more logs, can you please run the following command on durin-nuc-01?

tar -czf /keybase/private/strib@github,kentobias/client-21686.tgz $HOME/.cache/keybase/keybase.kbfs.*

(You can ignore any errors about the file being updated during this command.)

Thanks!

[l1a]

Done.

[strib]

Thanks! I put up #21720 for review which should fix this -- it looks like you got unlucky with a crash/restart at a sensitive time.