oats

Cargo diapers

Rocks, snails, sand, bottle caps, so many possibilities!

Yes, they like to .mov it .mov it

Extremely simplified:

Your file system consists of a whole lot of blocks to write data to. Let’s say you have a block size of 512kB, so a 4MB file would span 8 blocks. A 3.7MB file would span 8 blocks, too, as the remaining space can’t get used otherwise.

Now to get what file exists on which blocks, there’s a large index table, consisting of a number of index nodes (shortened to inode). Each inode saves multiple data fields of a file, like its name, owner, creation data, and the files blocks.

If you link a file to a second name (hard link) a second inode will get created that points to the same blocks.

That’s about it. Used to be important to chose the right inode size and count on filesystem creation for the average data you’ll save on the filesystem, as inodes have a fixed count, and the index table takes disk space, too. Too many inodes and you waste space that you could use for precious data, too few inodes and you can’t save new files even when you have free data blocks. With growing disk sizes people just went with massive indexes, who cares about a few wasted megs.

Modern filesystems (like ext3 and up) introduced journals, which complicate things.

You mean like in your kitchen? Too much metal, you’ll damage your magnetron.

You could use thermite and melt it to a pulp. Dangerous as well, though.

Really, just encrypt. Your CPU has AES extensions, performance impact is negligible. Simple, clean, and a protection against involuntary decommission as well.

You can lazy umount, which blocks new accesses and actually unmounts when it can

You used Solaris when cortana was already a thing? That’s great! :D

My university ditched Solaris like 20 years ago. Still have fond memories of cde lol

“I’ll get to it, eventually” would ruin the meme but be more fitting, in my opinion.

Had multiple occasions where people fought against filling disks and just couldn’t see why. Well, that 10 gig log file you deleted two weeks ago? It’s 20 gig now, and still being written to.

lsof shows stuff like that.

Nah, they just throw away the block markings, absolutely.

Overwriting a SSD is difficult as well, better encrypt the drive and trash the key when you decommission.

Well actshly, rm removes the inode, not the file. If it’s still in use it’ll stay on the disk until the last fd is closed.

• with most file systems that are usual on linux

Expenses. Have none when you can’t pay

You’re saving a lot of money that way

Filesystem doesn’t really matter once you have a reliable, redundant off-site backup and recovery plan set up and tested.

Really, use what fs feels best for you. And do your backups.

Did I mention backups are important?

I call my AI “ctrl-a delGPT”

Yeah, except if you’re outside our borders, then our frontex will sink your dinghy in the ocean. Happy drowning!

If windows is 100% nightmare, Ubuntu is like 5 to 10% that. While other distros are 0 to 1 percent.