keybase / keybase/client

Unable to re-enable journaling

Open
#22,869 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

As stated in the docs [1] , I know the journal can be disabled globaly and per TLF.

echo 1 > /keybase/private/me,you/.kbfs_disable_journal
echo 1 > /keybase/private/me/.kbfs_disable_journal

While running some tests I disabled the journal, but now I can't enable it back.

I 've tried with echo 1 in the above commands and restarting the KBFS, running 'kbfsfuse' with the parameter '-enable-journal' but I keep getting the following messages in the logs.

$ grep -i journal .cache/keybase/keybase.kbfs.log
2020-03-03T15:33:12.131924-06:00 ▶ [DEBU kbfs journal_manager.go:545] 065 Enabling existing journals (Background work enabled) [tags:KBFSINIT=WsRh3uAnrOF9LHM1M-zUOg]
2020-03-03T15:33:12.132290-06:00 ▶ [DEBU kbfs journal_manager.go:628] 066 Skipping file "config.json" [tags:KBFSINIT=WsRh3uAnrOF9LHM1M-zUOg]
2020-03-03T15:33:12.132352-06:00 ▶ [DEBU kbfs journal_manager.go:775] 067 Done enabling journals [tags:KBFSINIT=WsRh3uAnrOF9LHM1M-zUOg]
2020-03-03T15:33:12.132384-06:00 ▶ [DEBU kbfs init.go:965] 068 Journaling enabled [tags:KBFSINIT=WsRh3uAnrOF9LHM1M-zUOg]
2020-03-03T15:35:06.951387-06:00 ▶ [WARN kbfs folder_branch_status.go:341] 352 Error getting journal status for 0a9fb76eadee9b7d8bce201802497716: Journal not enabled for 0a9fb76eadee9b7d8bce201802497716 [tags:FSID=hkc9uozieBWRBcmsYE_3cA]
2020-03-03T15:35:06.952564-06:00 ▶ [WARN kbfs folder_branch_status.go:341] 355 Error getting journal status for 0a9fb76eadee9b7d8bce201802497716: Journal not enabled for 0a9fb76eadee9b7d8bce201802497716 [tags:FSID=keu-50cyJd9UAqlxwz11Tg]

0a9fb76eadee9b7d8bce201802497716 correspond to my private folder /keybase/private/mgonzalezm

any help is appreciated.

[1] https://keybase.io/docs/kbfs/understanding_kbfs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the KBFS journaling documentation linked in the issue, then inspect journal_manager.go and folder_branch_status.go at the logged lines. Reproduce the disable/enable sequence and compare the journal status with the logs; done means journaling can be re-enabled for the affected private folder without the reported warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.