For example once I had a bad cable, and it did a kinda sneaking silent damage. Let’s say 5 or 50 broken files every day. And only after some weeks I noticed some of them, and there was hardly a chance to identify them each day. And sometimes there was damage to the file system, too. It took a while find the root cause.
Today I use ZFS with redundancy and it does the recovery all by itself and my sleep is so much better :-)
“Proper backups” imply that you have multiple backups and a backup strategy. That could mean, for instance, that you would do a full backup, then an incremental/differential backup each week and keep one backup for each month. A bad cable would cause you trouble, no doubt, but the impact would be lessened by having multiple backups points spread over months.
Redundancy is not backup. Read that again.
Redundancy is important for system resilience, but backup is crucial for continuity. Every filesystem is subject to bugs and ZFS is not special. Here’s an article from a couple of days ago. If you’re comfortable with no backups just because you have redundancy, more power to you. I wouldn’t be.
Sure, all the work you do between the moment of the filesystem failure and the last backup is gone. There’s nothing that can be done to mitigate that fact, other that more frequent backups and/or a synchronized (mirror) system.
Backups are just a simple way to keep you from having to explain to your partner that you lost all the pictures and videos you took along the years.
For fun and learning. It’s just another tool to go with file level backup.
And the backup for this is 40mb and really fast, but backing up files even when compressed would be hundreds of GB, maybe terabytes, and then you’re paying for that amount of storage online somewhere, uploading for hours…
Picture this: you open and edit one of your documents and save it.
The filesystem promptly allocates some blocks and updates the inodes. Maybe the inode table changed, maybe not. Repeat for some other files. Now your “inode backup” has a completely different picture of what is going on on your disk. If you try to recover the disk using it, all you will achieve is further corruption of the filesystem.
I’m rocking two dailys right now. Tumbleweed and Nixos. I jabe tumbleweed on my work laptop as well as one laptop at home. Rock solid go to that I trust for all the things. I started using nix on a number of other machines at home a few months back, and I’m really really enjoying it!!
Early 2000’s I took a class in highschool called “What’s in the box”. A buddy of mine and I would hangout after school just talking and building computers. He showed me Lindows. I specifically remember looking at the clock in the dock, and thinking… “Wow!!! Look how you can customize the clock so much!”
It stuck with me. Shortly there after I dabbled with Suse. Then moved to Ubuntu. By 2005 I was almost exclusively using Linux on all my machine. Had one machine running windows for gaming, but the other machines I had were all Linux.
It’s only been around for less than a year as far as I’m aware and from what I gather still seems to be finding its sea legs as far as balancing between what rolls in immediately(ish) and what comes in through the big “tumbles”
Accidentally wipes out Mint last week, but have been meaning to try out Fedora 39 Plasma. So far, I love it. I have been really busy recently, but it has been a great system so far. My SteamDeck really made me fall in love with Plasma.
I never particularly cared for the Unity desktop. The first few times I tried it, there were hardware incompatibilities, slow performance, and crashing. Gnome3 is a complicated mess. I prefer to keep it simple. XFCE is fine for me.
I’m using docker packages for Doom Emacs. The main one is docker.el. On top of being faster and easier to use than the cli, you can also do some pretty neat stuff like use dired+tramp to browse files and open them in Emacs.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.