snapper
httm
snapper | httm | |
---|---|---|
33 | 98 | |
830 | 1,204 | |
1.7% | - | |
9.0 | 9.9 | |
8 days ago | 7 days ago | |
C++ | Rust | |
GNU General Public License v3.0 only | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
snapper
-
Bcachefs Merged into the Linux 6.7 Kernel
I left SUSE close to the end of 2021, and I had had to reinstall my work laptop twice that year alone. I consider that recent enough to call it current.
> df is not lying
To me, that reads as "df isn't lying because $EXCUSES."
I disagree. I don't care about excuses. I want a 100% accurate accounting of free space at all times via the standard xNix free-disk-space reporting command, and the same from the APIs that command uses so that applications can also get an accurate report of free space.
If a filesystem cannot report free space reliably and accurately, then that filesystem is IMHO broken. Excuses do not exonerate the FS, and having other FS-specific commands that can report free space do not exonerate it. The `df` command must work, or the FS is broken.
The primary point of Btrfs is that it is the only GPL snapshot-capable FS. The other stuff is gravy: it's a bonus. There are distros that use Btrfs that don't use snapshots, such as Fedora.
Some Btrfs advocates use this to claim that the problems are not problematic. If the filesystem is of interest on the basis of feature $FOO, then "product $BAR does not exhibit this problem" is not an endorsement or a refutation if $BAR does not use feature $FOO.
Btrfs RAID is broken in important ways, but that is not a deal-breaker because there are other perfectly good ways of obtaining that functionality using other parts of the Linux stack. If no feature or functionality is lost considering the OS and stack as a whole, then that isn't a problem. However, this remains serious and an issue.
Additional problems include:
• Poor integration into the overall industry-wide OS stack.
Examples:
- Existing commands do not work or give inconsistent results.
- Duplication of functionality (e.g. overlap with `mdraid`)
• Poor integration into specific vendors' OS stacks.
Examples:
- SUSE uses Btrfs heavily.
But SUSE's `zypper` package manager is not integrated with its `snapper` tool. Zypper doesn't include snapshot space used by Snapper in its space estimation.
Snapper is integrated with Btrfs; licence restrictions notwithstanding, I would be much reassured if Snapper supported other COW filesystems.
(This has been attempted but I don't think anything shipped -- https://github.com/openSUSE/snapper/issues/145 . I welcome correction on this!)
The transactional features of SUSE's MicroOS family of distros rely heavily on it. This lack of awareness of snapshot space utilization deeply worries me. I have raised this with SUSE management, but my concerns were dismissed. That worries me.
Red Hat removed Btrfs support from RHEL. As a result it has had to bodge transactional package management together by grafting Git-like functionality into OStree, then building two entirely new packaging systems around OStree, one for the OS itself and a different one for GUI-level packages. The latter is Flatpak, of course.
This strikes me as prime evidence that:
1. Btrfs isn't ready.
-
Desktop Linux Hardening
Very useful. One practical thing to add: enabling automatic snapshots (e.g. with https://github.com/openSUSE/snapper), ideally backing them up separately (e.g., with borg) might help recovery.
-
best practice to keeping Linux environment 'clean'?
I like btrfs snapshots, e.g. with snapper (http://snapper.io/), but that needs a bit of setup (and is out of the box with some distros, e.g. opensuse).
-
New user: some small issues
Use snapper, it's very good and it can be integrated with grub so that you can boot into an snapshot (not sure you can do that with timeshift).
-
Snapper: Trouble setting up /.snapshots mountpoint for custom subvol location
The other big difference, is that I would like to have "flat" hierarchy (at least within the nested distro-specific subvol) for my snapshots. Meaning that I do not like the nested structure of /.snapshots that snapper seems to assume by default and would prefer something like /fedora/snapshots/rootfs instead. It seems this is a somewhat popular request that has been opened for over 8 years... but since it hasn't been implemented in snapper itself, most people just use workarounds.
-
New high-end gaming PC build, need distro suggestion
If, for some reason, anything goes wrong with your system, it is also trivial to return it to a working state, using snapper. This is preconfigured by default, no manual work required.
-
Best configuration for bare hypervisor distro FOR DESKTOP VMs
Are you sure you need a full on virtual machine, rather than a system snapshotting tool like Snapper or Timeshift?
-
snapper list -show-items-about-to-be-deleted, have anyone done it?
I never said it did. Please read. It was meant to demonstrate that the health of the project is questionable, since after thatf ater that change was submitted, the official tests for the project is broken (see the current status on their github page https://github.com/openSUSE/snapper).
- How do you prefer to backup and restore your Fedora system?
-
Just try it, it's glorious
The amazing tooling: - YaST, the best configuration tool out there. I think its fair to say that nothing comes close to the number of things you can configure with Yast. - Open Build Service (OBS), a tool that automatically builds binaries for software and sets up repositories to add to your favorite package manager. Supports every major linux distro but intergrates especially well with the openSUSE software store, and OPI (openSUSE equivelant to something like paru or yay) to be like the AUR but (imo) better. - openQA, Automated testing for any package or operating system, making sure that even on leading edge software, you're still stable. - snapper, out of the box btrfs snapshots that make sure you can (almost) always boot into a useable system, even after a bumpy update.
httm
-
Is my open-source project up to date with MIT license compliance and attribution?
My projects and many projects include a THIRD-PARTY-LICENSES.html file when I distribute binaries. See: https://github.com/kimono-koans/httm/blob/master/third_party/LICENSES_THIRD_PARTY.html
-
ZFS and Proxmox Questions
The only real advantage I can think of with nested ZFS is that the files in the KVM would obviously be individual inodes in the nested ZFS filesystem and datasets, in addition to the one inode per virtual volume on the hypervisor (or zvol). This would allow for granular file management on the kvm and the use of tools like https://github.com/kimono-koans/httm which is like a command line time machine for ZFS.
-
ZFS silent corruption bug found: replaces chunks inside copied files by zeroes
> It's worth noting that copy_file_range is used by a lot of things.
Yes, but the trigger feature, block cloning, only landed in the latest 2.2 release. If you immediately hopped on 2.2, and used a system with lots copy_file_range and FICLONE use, yes, you may have a problem (like, as you note, on Gentoo, where this problem surfaced).
Most people were just hopping on the bandwagon. My distro ships 2.1.5, so I have a 6 month wait until this feature lands, so I was just building copy_file_range support into my ZFS apps, right before news of this bug hit.[0]
> There are other things required to trigger the bug that are a lot less common though.
Exactly. My guess is the incidence of this will exceedingly rare for the common user/small NAS user/etc. I've run a corruption detector[0], and what I've found mostly indicates false positives. Some are build artifact fingerprints, which I don't care about, and which were deleted with the next build. The ones with an extant file on another system, I confirmed were a diff match with the origin using `rsync -rincv` and whats on snapshots with `httm --map-aliases`. So far no positive matches.
[0]: https://github.com/kimono-koans/httm
-
Are you running Linux with a filesystem capable of block cloning/FICLONE (ZFS >= 2.2, XFS, BTRFS)?
cargo install --git https://github.com/kimono-koans/httm --branch clones strace -f -o stderr.txt -e ioctl -- httm -r -R ~/.zshenv
- ZFS for Dummies
-
Workflow: Rolling forward with ZFS and `httm`
httm prints the size, date and corresponding locations of available unique versions (deduplicated by modify time and size) of files residing on snapshots, but can also be used interactively to select and restore files, even snapshot mounts by file! httm might change the way you use snapshots (because ZFS/BTRFS/NILFS2 aren't designed for finding for unique file versions) or the Time Machine concept (because httm is very fast!).
-
Really no easy GUI Btrfs snapshots for Fedora 38?
All btrfs snapshot tools can have different layouts. It's mostly a nightmare for any one tool to support. Although its not the tool you're looking for, FYI AFAIK httm supports all/most btrfs layouts, but it took more work than necessary to get there.
- Why there is no tool that shows how file is changed over time across snapshots?
-
Bcachefs – A New COW Filesystem
ZFS only option which requires super user privileges.
[0]: https://github.com/kimono-koans/httm/blob/master/httm.1
-
What's a really niche tool you use that you can't live without?
httm - Interactive, file-level Time Machine-like tool for ZFS/btrfs/nilfs2
What are some alternatives?
TimeShift - System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
fzf-fish-integration - 🔍🐟 Fzf plugin for Fish
btrbk - Tool for creating snapshots and remote backups of btrfs subvolumes
dotfiles - My dotfiles
zfs - OpenZFS on Linux and FreeBSD
snapper-gui - GUI for snapper, a tool for Linux filesystem snapshot management, works with btrfs, ext4 and thin-provisioned LVM volumes
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption
Rsnapshot - a tool for backing up your data using rsync (if you want to get help, use https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss)
reflex - Run a command when files change
snap-sync - Use snapper snapshots to backup to external drive
awesome-rust - A curated list of Rust code and resources.