We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Dropbox is compatible with Ext4 but doesn't recognize ext4 drive?
So, like most Linux users, I've gotten the message about needing to upgrade to an ext4 drive. I had an extra drive in my machine with nothing on it so I formatted it to ext4. I rebooted then went int...
I've found a workaround. Create a new folder within the mount point of your ext4 drive. Then, simply choose that folder as the target in the Dropbox app. Here's an example:
Mount point of ext4 drive:
/media/mynewdrive
Make new directory within the mount point, say "DropboxContainer". Now choose the following path (simply choose in the Dropbox GUI) as the sync target:
/media/mynewdrive/DropboxContainer
To confirm, your Dropbox sync folder would look like this:
/media/mynewdrive/DropboxContainer/Dropbox
In my case, it used to complain about the ext4 thing, but this workaround seems to have done the job. Please let me know if it works for you.
This solution did the trick for me, too. Thanks @AminSadeghi
Ah in the last 2 days the problem has magically returned again, after working with no problem for a month (it happened at the same time on 2 machines).
No idea what has changed. I presume it is a remotely activiated restriction. I'm sure I've not changed anything, after my gparted fiddle a month ago (posted earlier 11-13-2018 12:17 AM which fixed the problem on all 3 of my linux machines I use).
They changed something, location doesn't even need to be on an ext4 drive anymore as shown in my fstab above. My Dropbox location is /home/XXXX/Dropbox which is an ext3 partition
Oh, I see. Are you saying that they've fixed it?
There has been an upgrade in the software so I think they did
Your workaround works for me with Ubuntu 18.04 fresh install
@pwang
What ... you needed to do the Gparted fiddle after your Ubuntu 18.04 install too ?Reading updates on other posts, Dropbox users say it may have updated recently and started working again that way. So I'm still not 100% if it was what I did with Gparted or an update.
Good that it is working though on 3 of my Ubuntu machines.
Maybe I will do a test VM in the future with a fresh install and see when it works.
AminSadeghi wrote:I've found a workaround. Create a new folder within the mount point of your ext4 drive. Then, simply choose that folder as the target in the Dropbox app. Here's an example:
Mount point of ext4 drive:
/media/mynewdrive
Make new directory within the mount point, say "DropboxContainer". Now choose the following path (simply choose in the Dropbox GUI) as the sync target:
/media/mynewdrive/DropboxContainer
To confirm, your Dropbox sync folder would look like this:
/media/mynewdrive/DropboxContainer/Dropbox
In my case, it used to complain about the ext4 thing, but this workaround seems to have done the job. Please let me know if it works for you.
This WORKED! Thank you!
AminSadeghi wrote:I've found a workaround. Create a new folder within the mount point of your ext4 drive. Then, simply choose that folder as the target in the Dropbox app. Here's an example:
Mount point of ext4 drive:
/media/mynewdrive
Make new directory within the mount point, say "DropboxContainer". Now choose the following path (simply choose in the Dropbox GUI) as the sync target:
/media/mynewdrive/DropboxContainer
To confirm, your Dropbox sync folder would look like this:
/media/mynewdrive/DropboxContainer/Dropbox
In my case, it used to complain about the ext4 thing, but this workaround seems to have done the job. Please let me know if it works for you.
This worked for me also (Ubuntu 18.04), and dropbox stopped complaining. Thanks!
But I still think it's kind of logical to have the sync folder in my home directory. By now the dropbox app is up to 67.4.83 and trying to switch back just gives me the original error message about the file system not being ext4 (which it is).
Does anyone have any ideas on how to put the sync directory back under home?
Same situation here. I'm very, very disappointed with Dropbox in this point :(
It's easier to change service than dealing with workarounds.If someone still have problems about selecting "Dropbox" folder, it seems known bug, that the application don't check only content, but also the pointed directory! This lead to problems when dropbox root is going to be directed to mountpoint directory. In such a case (because of wrong check - bug in fact) dropbox confuses and make wrong conclusion. One workaround could be: selected directory must be IN the ext4 partition, not the root of this partition (doesn't matter how deep in directory tree is this). It seems most people just select the root, what trigger the bug. The mountpoint (FS root) directory could be (and usually is) outside ext4 partition, mounted in this point! It seems that the dropbox people will not fix this, so... be careful.
Another (more general) solution is 'fixing' this FS check using this script, so doesn't matter anymore where You try to set the dropbox folder (even outside ext4 partition or using eCriptFS).
Good luck for everyone!
