snapper
openzfs
snapper | openzfs | |
---|---|---|
33 | 25 | |
830 | 364 | |
1.7% | 4.4% | |
9.0 | 9.7 | |
8 days ago | 12 days ago | |
C++ | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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.
openzfs
-
WinBtrfs – an open-source btrfs driver for Windows
Heads up, installing both WinBTRFS and OpenZFS on Windows may have problems:
"Win OpenZFS driver and WinBtrfs driver dont play well with each other"
https://github.com/openzfsonwindows/openzfs/issues/364
-
OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
I tried it a few months ago and ReFS ate my data. No indication of why in event logs or SMART data. It had IsPowerProtected set because I have a UPS and I had a unclean restart, I would expect it to lose data, but not to corrupt the filesystem metadata. I had a backup of the data but wanted some recent changes. Refsutil (the official Microsoft tool) didn't help because it has not been updated for the newest ReFS version. I couldn't read most files because I had integrity enable and files failed the check. Hetman's Data Recovery was able to recover most of the data. In later testing I found out that IsPowerProtected is just very unsafe. I have since put some time into testing and sometimes fixing https://github.com/openzfsonwindows/openzfs , it is not ready for use yet, but it is making great progress.
-
Is there a mount backup vdev Windows tutorial
Windows lacks support in the same sense that Linux lacks support; there are external projects implementing it for both, though I believe the Windows port is less polished. (Some people are running it in production, though...)
-
Windows on Btrfs
This is really cool and speaks to the modularity of the Windows file system stack. I love projects that customize Windows (working against its closed-source nature).
There’s an OpenZFA port to Windows[0]. I wonder if my hopes of having ZFS on Windows (including the boot drive, because I would love to be able to snapshot and rollback) would actually be possible.
[0] https://github.com/openzfsonwindows/openzfs
-
External Harddrive from NAS to Windows?
*cough* it can, but... no idea how well it works but it seems a bit hacky.
-
External Harddrive from Truenas to Windows?
If you have not used it, maybe the native ZFS port for windows could be an easier solution.
-
Problem with a NVMe device: it drops off the bus on intense IO, so I can't scrub or zfs send
Theoretically ZFS is ported to windows, but I heard that it is not really stable yet.
- windows) IO error and suspended
-
ZFS on Windows: Mapping \*nix UID/GID ⇹ Windows UUID?
I did use the packages provided here: https://github.com/openzfsonwindows/openzfs/releases/tag/zfswin-2.1.6rc2
- Anyone using openzfs on Windows on a daily basis? Can ZVOLs be used to back WSL?
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.
zfs - OpenZFS on Linux and FreeBSD
btrbk - Tool for creating snapshots and remote backups of btrfs subvolumes
ZFSin - OpenZFS on Windows port
btrfs - WinBtrfs - an open-source btrfs driver for Windows
snapper-gui - GUI for snapper, a tool for Linux filesystem snapshot management, works with btrfs, ext4 and thin-provisioned LVM volumes
openzfs - OpenZFS on Linux and FreeBSD, and, macOS. This is where development for macOS happens.
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)
windows-driver-docs - The official Windows Driver Kit documentation sources
snap-sync - Use snapper snapshots to backup to external drive
go-zfs - Go wrappers for ZFS commands