Data loss in the macOS app—please help

Questions & Help
1

I just experienced a bunch of data loss in the macOS app. I’m assuming i’m out of luck but figured I’d ask you kind folks.

I store my graph in Google Drive which I mount as a drive on macOS. Logseq isn’t aware of Google Drive itself, just where the files live on disk.

  1. I started to notice that images were showing up as broken
  2. Soon after, I got an error that said the app could no longer find the files on disk, putting me in read-only mode as such
  3. I unlinked and relinked my graph to try to fix, believing this was a non-destructive action
  4. After re-linking, my past four days of content were no longer in Logseq
  5. I looked on disk and it appears that those files were never there (nor in my trash, etc.)
  6. This suggests that Logseq had multiple-days-worth of content in memory only?

That struck me as hard to believe but I can’t think of what else could have happened here.

Any caches or anywhere else I can look for these files?

2

There are known issues with using third-party sync services and Logseq—especially used in combination with Logseq Sync.

Do you use Logseq Sync? Because in that case you should stop syncing using Google Drive immediately. This is also mentioned in the Sync onboarding guide:

CleanShot 2023-02-10 at 19.43.21
CleanShot 2023-02-10 at 19.43.21999×393 60.6 KB

Te recover your data, there are two options:

  1. Go to the folder where you’ve stored your graph and look for the missing data in the logseq/bak folder.
  1. (Only if you use Logseq Sync) Go to the page(s) in question and click ... → View page history to roll back to a previous version. From the Sync manual:

CleanShot 2023-02-10 at 19.47.02
CleanShot 2023-02-10 at 19.47.021007×603 54.6 KB

I hope this helps!

3

Hi,

Thanks so much for getting back to me.

I don’t use Logseq Sync at all.

Unfortunately logseq/bak does not contain anything recent at all. The newest journal in that folder is from seven months ago.

Any other suggestions?

-Bryan

4

With third-party services it’ll complicate things as we don’t know what’s exactly happening. But I’ve asked an engineer to look into this report.

Can you please help us in the meanwhile by providing more info:

  1. What version(s) of Logseq do you use?
  2. What devices do you use Logseq with?
  3. Are there any other devices that have access to the Google Drive folder in question?
5
  1. Version: 0.8.16
  2. Devices: MacBook running macOS Ventura
  3. Other devices with Google Drive access: An iPhone is logged into that account in the Google Drive app but Logseq iOS is not connected to it
6

@irace You might find some helpful information here;