• stupidcasey@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    1 day ago

    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.

    • beegnyoshi@lemmy.zip
      link
      fedilink
      arrow-up
      5
      ·
      1 day ago

      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 ~

    • Geometrinen_Gepardi@sopuli.xyz
      link
      fedilink
      arrow-up
      7
      ·
      2 days ago

      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?

      • Morphit @feddit.uk
        link
        fedilink
        arrow-up
        12
        ·
        2 days 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.

      • Hupf@feddit.org
        link
        fedilink
        arrow-up
        6
        ·
        2 days ago

        That would be a separate step (send/receive).

        But rm -r when you created a snapshot before basically just adds metadata about which files are supposed to be deleted in the current version. The snapshot still has the old filesystem content.

        That also means that when you use up all your space, deleting files actually worsens the problem.

  • plsnerf7@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    2 days 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…

  • jimerson@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    2 days ago

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

  • B-TR3E@feddit.org
    link
    fedilink
    arrow-up
    9
    ·
    2 days ago

    rm -rf is always right. No matter where. Supposed, of course, you are root.

    No discussion. I am root! I am always right!

  • UnfortunateShort@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days 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