Comments
-
I think that’s purely precautionary advice, since the reality is Arch isn’t officially supported. I’ve already explained what I think is the cause (based on how I was able to resolve) and that I believe it’s kernel-related (I actually used the Fedora example as well) to support, so hopefully a fix comes out soon.
-
I can confirm that a wrapper around Dropbox via LD_PRELOAD which replicates the pre-7.2 btrfs ID reporting solves the issue. So at least in my case this does appear to be related to changes in btrfs behavior.
-
Hey @vankyan, for my own troubleshooting, do you mind confirming some basic details about your setup? Are you on Linux kernel 7.2 and is that when your issues started? Are you using btrfs and do you have a multi-drive/disk setup?
-
I performed strace runs of Dropbox both immediately after rebooting (when the problem occurs) and after restarting Dropbox (when it doesn't), and might have narrowed the cause down to a change in btrfs behavior between 7.1 and 7.2. With Linux 7.2 (commit c2a74ed0494c), btrfs's statfs() filesystem ID includes the…
-
Actually, I believe I created one this morning after speaking with the support bot, though I haven't spoken to anyone yet. The ID is 26662235.
-
Ah, sorry about that. Thank you for removing.
-
Hi Jay, My Dropbox folder is located on an internal drive using the default location (/home/<username>/Dropbox). I'm attaching a zipfile of my ~/.dropbox/logs folder from this morning, which I believe should capture at least one of the failures. [Removed as per Community Guidelines]
