The heart skip when an rm command runs longer than expected.
post
ctrl-c ctrl-c ctrl-c ctrl-c ctrl-c
i ctrl+c my fucking face off when that happens.
oh and in case y'all can't read it, the command is cat * in /bin
How do I stop some big mean missed command from tearing up my main drive?
The answer: Use Ctrl-C. And if that don't work, use more Ctrl-C.
And if that don't work? Use Ctrl-Z.
Btrfs snapshots to the rescue!
I've been meaning to tinker with Brfs. Is the idea that snapshots live on a separate volume so you can always recover a messed up system?
There are tools like snapper and btrbk that periodically make snapshots. Since btrfs is a COW filesystem, the live subvolume just stores newer changes on top of the snapshot β it doesn't need to copy anything until it changes. Only when file data is no-longer referenced is it actually marked free to overwrite. This can make disk usage a bit un-intuitive since you can have large files stuck in snapshots that don't show up in your live subvolumes but still use up space. It can really save you from serious mess ups and is really cheap in terms of performance. It's also possible to send snapshots over a network to another machine if you want longer term backups without keeping them on local disks.
When I paste a 250k-line log to console.
"The right command in the wrong directory can make all the difference in the world. So rise and shine, Mr. Tux. Wake up, and check the log files..."
I heard this in G-man's voice from the first two or three words!
Last week βI was trying to fix somethingβ and made some bad decisions. Long story short, wrong command in the right directory the screen flashed like in this memeπ. Well, I liveUSB to reinstall the whole thing. Then I remembered that I installed Cachy with BTRFS snapshots. Bam Fucking magic, it's like nothing happenedβ¦ I call it the Ohh shit, Ctrl-Z OS troubleshooter. Yep I'm new in linux...
Made that mistake last week. Luckily it was just a chmod and not a rm. Stomach did a flip regardless.
oh i made that same mistake a month ago when trying to chmod 777 -R another partition... and ran it in / instead
Luckily it was just a chmod
that can still render a system unbootable π
I was trying to sudo rm -rf ./ Once and missed the / so I just used rm -rf . And this was before they added --no-preserve-root as a default so it just ripped through my entire drive.
sudo rm -rf ./ and sudo rm -rf . are, as far as I know, the same command. Did you mean that you dropped the . and ran sudo rm -rf /?
Fortunately for me, this never happened to me, but I have gotten pretty close to running rm -rf ~ after mistakenly creating a directory caller ~...
after mistakenly creating a directory caller ~β¦
How do you even delete such a directory?
I recently noticed that the logging framework I use does not limit the log's length. I don't know how exactly I filled the memory so quickly, but I did

top 32 comments