top 32 comments

sorted by: hot top controversial new old
[–] 105 points 10 months ago (2 children)

The heart skip when an rm command runs longer than expected.

  • source
  • hideshow 2 child comments
  • [–] 71 points 10 months ago (3 children)

    ctrl-c ctrl-c ctrl-c ctrl-c ctrl-c

  • source
  • hideshow 3 child comments
  • [–] [S] 52 points 10 months ago (2 children)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 24 points 10 months ago (2 children)

    Btrfs snapshots to the rescue!

  • source
  • hideshow 2 child comments
  • [–] 9 points 10 months ago (1 child)

    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?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 14 points 10 months ago

    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.

  • source
  • parent
  • [–] 21 points 10 months ago (1 child)

    When I paste a 250k-line log to console.

  • source
  • hideshow 1 child comment
  • [–] 38 points 10 months ago (3 children)

    "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..."

  • source
  • hideshow 3 child comments
  • [–] 18 points 10 months ago
    [–] 15 points 10 months ago

    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...

  • source
  • [–] 13 points 10 months ago
    [–] 8 points 10 months ago (4 children)

    Made that mistake last week. Luckily it was just a chmod and not a rm. Stomach did a flip regardless.

  • source
  • hideshow 4 child comments
  • [–] 8 points 10 months ago (5 children)

    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.

  • source
  • hideshow 5 child comments
  • [–] 6 points 10 months ago (4 children)

    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 ~...

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 10 months ago

    I've aliases sudo rm to sudo rm -i

  • source
  • [–] 2 points 10 months ago

    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

  • source