to be clear, this time it started uploading files too, though it appears it skipped all markdown files though I paused it while it was churning so no idea. Lots of clean up to perform now… Really wish I had good logs and this is one of those times I really really wish this was open source ( Open Sourcing of Obsidian - #312 by dazinger ) because I’d have done more to resolve it almost a year ago.
Edit:
So now I’ve spent 2 hours cleaning things up, but being careful to catch failure info. I suspect my case may be related to an issue in the filesystem but I do not know. I have for some time suspected the nvme in this computer to be on it’s way out.
Here are some syslogs from when I deleted files on another computer, saw that the sync logs noted they were deleted on this computer (the one which I turned on, starting this mess). However, the files still exist on this computer..
2026-01-02T23:42:40.121044-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: GFileInfo created without standard::name
2026-01-02T23:42:40.121237-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached
2026-01-02T23:42:40.121506-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: GFileInfo created without standard::name
2026-01-02T23:42:40.121781-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached
2026-01-02T23:42:40.122091-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: GFileInfo created without standard::name
2026-01-02T23:42:40.122365-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached
2026-01-02T23:42:40.122685-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: GFileInfo created without standard::name
2026-01-02T23:42:40.122955-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached
2026-01-02T23:42:40.123236-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: GFileInfo created without standard::name
2026-01-02T23:42:40.123574-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached
2026-01-02T23:42:40.123906-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: GFileInfo created without standard::name
2026-01-02T23:42:40.124181-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached
2026-01-02T23:42:40.124685-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: GFileInfo created without standard::name
2026-01-02T23:42:40.124935-07:00 tj-ThinkPad-X1-Carbon-6th-v3 gvfsd-trash[3835]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached\
Edit:
Man I was supposed to be well asleep an hour or two ago. I only turned this damned computer on to synch the work to it that I had done elsewhere so that it would be ready for tomorrow (it’s my mobile one). Can we PLEASE FIX SYNC???
Edit:
It’s now almost 1 and I’m still at it because I’m finding other dupicates which must have been left over from previous bad synchs.
Please fix this… That or I want a refund for time spent fixing issues due to synch and lack of logging. However, at my usual pay, the hours I’ve spent over the last year fighting with synch has cost far more than what I paid for sync, and I basically went with your tool over some homebrew or db based one because I WANT to pay the team building a tool I use daily. Money is tight and this was a conceous decision and I would far prefer a synch I could trust with my personal data.
If I had to hypothesize I would guess you’re not using a good transaction log in sync. If this is the issue, please understand the importance of logging in production software. If I’m going to pay for Sych rather than use my own distributed filesystem or database, I’d expect production practices like good logging and a synch tool that utilizes standard distributed db logic like Cassandra’s Log-Structured Merge-Trees (LSM-Trees) and Tombstones (see: Tombstones | Apache Cassandra Documentation ).
please please please please pretty please prioritize investment in the synch logic!
I routinely suggest Obsidian to my collegues, customers, friends, and family, and my experience with the synch tool, lack of logging, and inability to actually root cause and resolve the issues has caused me to regret that with shame. I have worked for 2 of the largest Linux / Open Source companies for the last decade so recommending a closed source tool with such critical production faults is a black mark on my professional reputation when there are opensource compettitors I could have recommended which we could be improving instead of just fighting with..
Obviously, I don’t expect you to care about my professional reputation, but I can’t in good conceous continue to recommend Obsidian until it at least has a working sync and logging ( Obsidian Sync: Persistent / Save Sync logs for debugging )..
Edit, another..
So the sync log is not showing unpause events. Can I please just pop in and add these or troubleshoot them? This is basic enough that it’s in the realm of things I’ve actually traced and fixed when I find issues in my company’s code while working with a customer.
Also, and I’m not sure if this is theme related or not yet, but the filter makes the sync log impossible to read as it adds a bunch of spaces seemingly before the word you are filtering for when it bolds them 
Final Edit for the morning. Almost 2 am and my plans for the night and day are shot. do not like. Thank you for keeping me company through it all. Hopefully some of what I saw helps. 