I have a similar setup and it works. So you are probably doing something wrong, I don't know what. Maybe look at dmesg for a filesystem error.
That is not a good method for testing. Maybe the filesystem still requires new files to be smaller than free space. Or maybe the file could be not really compressible, for example, you won't be able to compress random data. You also won't compress already compressed data, like videos.
You could write a real text file of some kB and then check the compression ratio with something like "compsize".
The mount command mounts the disk with the options you give to it but only once. Now, because you don't want to manually run mount everytime you use your disk, you must set it up so it is always mounted with the options you want. Udisks2 is one of the tools for that.
edit: apparently compsize is btrfs only. You can use "du" with and without --apparent-size and check the differenze
It's like the difference between "sex" and "orgy"
The show was already cancelled when they were making season 3, so they rushed all the planned future stuff into it.
Charlie! You look quite down
With your big sad eyes and your big sad frown
Life doesn't have to be so blueeeee!
Put a banana in your ear
A banana in my ear?
Put the right banana right into your favourite ear
It's true!
Says who?
A banana in your eeeeeeeeeEEEEEEEEEeeeeeeeaaar
So, first of all, there is no gui for this, that I'm aware of, so you will have to do it from terminal. Second, on f2fs, compression works that you don't enable compression for a folder, instead you mount the drive with compression enabled, and new files will be compressed automatically.
So what you need is to set up your disk to be mounted with compression. There are many paths you can follow here. If you want your drive to be (almost) permanently connected, the easiest way is to use "/etc/fstab". If you want to use it as a regular SD card, mounting and ejecting it from your file explorer etcetera, then you should go here and learn how to have udisks2 mount your device with compression, which should be what your desktop environment uses to mount drives. I suggest you set that up for your specific device, and not for all f2fs devices. Good luck.
You can look up other useful f2fs options on the arch wiki. I suggest you add all those options that reduces writes to your disk and improve durability (like lazytime).
You should use zstd as compression algorithm, and because this is a slow and small drive, you can crank up the level of compression.
If you manage to pull this off, the next time you install a (bigger and faster) drive on your pc, you can try to look into zfs.
If it's a flash memory (sd card, usb stick, ssd, etc), you could try f2fs, it's very light, and it supports compression and is meant specifically for that kind of devices (well, more for ssds).
But judging your experience from your comments, I suggest you don't delve into niche filesystems until you have more experience with Linux, especially for something like 128MB. I especially suggest you avoid zfs for now.
You can buy an usb-powered one for a couple euros from AliExpress, or you can hook 5V to an original bar. But the bar itself is just two Infrared lights, there's plenty of substitutes (i.e. literally two candles 20cm apart).
P.s. do not leave the bar permanently on, you will burn out the LEDs. The Wii turns it off with the console
P.p.s. you can configure esperto-wiimote to run a command when you connect the First wiimote, and disconnect the last. It's meant for turning on and off the bar, if you can do it programmatically
I have an announcement to make.
Shadow the hedgehog is a bitch!
He pissed on my fucking wife. It's true, he took out his hedgehog dick and pissed on her. And then he said it was "this big" and I said "that's disgusting!"
What doesn't kill you, will do it later