I am using Dropbox on an ext4 file system, but it doesn't seem to understand that it really *is* an ext4 file system. And I can confirm that xattr's are enabled. From my Dropbox folder: <tytso@cwcc> {/home/tytso/Dropbox} 77% getfattr calendar.pdf # file: calendar.pdf user.com.dropbox.attributes Now, Dropbox is running inside a container using bind mounts, because I don't trust random binaries downloaded from the network having complete and free run of my system. But it is indeed an ext4 file system, despite Dropbox complaining thinking that it isn't. From inside the container: <tytso@cwcc> {/home/tytso/Dropbox} 79% docker exec -i -t dropbox /bin/bash root@cwcc:/dbox/Dropbox# ls -l calendar.pdf -rw-r--r-- 1 dropbox dropbox 131349 Nov 7 05:47 calendar.pdfroot@cwcc:/dbox/Dropbox# df -h . Filesystem Size Used Avail Use% Mounted on /dev/mapper/cwcc-root 366G 185G 163G 54% /dbox/Dropbox root@cwcc:/dbox/Dropbox# grep /dbox/Dropbox /proc/mounts /dev/mapper/cwcc-root /dbox/Dropbox ext4 rw,relatime,errors=remount-ro 0 0 I understand that running Dropbox inside a docker container is probably not what you would consider "a supported configuration". But I can assure you that in fact the Dropbox folder is using a supported file system (ext4, with xattr's enabled). P.S. Dropbox isn't really running as root; it's inside a user id namespace as well. P.P.S. In case you're curious, here's how I'm setting up the Dropbox container: https://github.com/tytso/docker-dropbox P.P.P.S. As the ext4 maintainer, I do appreciate your support of the ext4 file system. I will point out that there are plenty of other file systems that support extended attributes as well, however.
... View more