this post was submitted on 28 Oct 2023
474 points (95.8% liked)

linuxmemes

24384 readers
896 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    474
    Saved my ass a few times (lemmy.dbzer0.com)
    submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 1 points 1 year ago (2 children)

    How is this different than a regular backup? Not salty, just curious.

    [–] [email protected] 5 points 1 year ago

    I believe it's using a feature built-in directly in the filesystem.

    I'm just curious if it's possible to browse individual snapshots like in MacOS Time Machine and fetch individual files out.

    [–] [email protected] 3 points 1 year ago

    Now mind you, everything I write might be wrong, I am out of my depth here.

    But as I understand a BTRFS snapshot is simply a (subvolume in which you will find) copy of the table that points to the actual files or, rather, blocks on your drive. As long as a table exists that points to a block, this block will persist.

    The nature of BTRFS is Copy-on-Write so in your active snapshot, when you modify a file / block, a copy of it is created with the new version, referencing this new block on the filesystem table.

    This is why BTRFS snapshots are fast and take little space by themselves, you do not need to actually copy all the data at the moment of creating the backup, rather when the data is modified and only that data.