The Linux ext4-only ultimatum: drop everything but one filesystem
August 2018 (enforced November 2018)
Dropbox told Linux users that from November 2018 its client would sync only on unencrypted ext4, abruptly stripping support for XFS, Btrfs, ZFS, and encrypted setups — communicated as a terse desktop notification with little explanation.
What happened
In August 2018 Linux users began receiving an in-app warning that, starting 7 November 2018, the Dropbox client would support only a single filesystem: ext4 on Linux (alongside NTFS on Windows and HFS+/APFS on Mac). Every other common Linux filesystem — XFS, Btrfs, ZFS, ext3 — would stop syncing, as would encrypted setups such as eCryptFS or LUKS layered under the folder.
The way the decision was delivered amplified the anger. Many users learned about it only through a small notification, with the underlying rationale — Dropbox's reliance on extended attributes to track files — surfacing mainly through community sleuthing and support-forum replies rather than a clear, proactive explanation. The carve-out for 'unencrypted ext4' particularly stung security-conscious users, who read it as Dropbox effectively penalizing those who encrypted their disks. XFS is the default filesystem on Red Hat Enterprise Linux, so the change hit professional and server users as well as hobbyists.
After sustained criticism, Dropbox partially walked the policy back: in July 2019 it restored sync support for ZFS, XFS, Btrfs (on 64-bit systems) and eCryptFS — but only after months in which Linux users felt treated as an afterthought.
Impact
The ext4 ultimatum became a rallying point for the Linux community's long-running sense that Dropbox neglected the platform, and a case study in how a poorly communicated product decision can do more damage than the technical change itself. It pushed many Linux users to self-hosted and open-source sync tools and hardened a reputation for abrupt, top-down changes; the eventual partial reversal showed the original scope had been broader than necessary.