bmap-tools
httm
bmap-tools | httm | |
---|---|---|
2 | 98 | |
222 | 1,213 | |
- | - | |
5.5 | 9.9 | |
about 2 months ago | 18 days ago | |
Python | 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.
bmap-tools
-
A data corruption bug in OpenZFS?
> But I recall reading elsewhere a discussion about some userspace program which did depend on holes being present in the filesystem as actual holes (visible to SEEK_HOLE and so on) and not as runs of zeros.
> treatment of on-disk segments as "what was written by programs" can cause areas of 0 to not be written by bmaptool copy
https://github.com/intel/bmap-tools/issues/75
IMO, the issue here isn't filesystem or zfs behavior, it's that bmap-tool wants an extra "don't care bit" per block, which filesystems (traditionally) don't track, and programs interacting with filesystem don't expect to exist.
Some of the comments I've made in this issue describe options to make things better.
-
ZFS silent corruption bug found: replaces chunks inside copied files by zeroes
(>_<) Oh man, I knew about [0] when I posted (which is why I said it just reduces the chance of hitting the bug (by a lot)). But after spending all Saturday JST on it, I went to bed before [1] was posted.
Skimming through #6958 though, it seems like it's the lesser of evils, compared to #15526... I think? It's less obvious (to me) what the impact of #6958 is. Is it silent undetectable corruption of your precious data potentially over years, or more likely to cause a crash or runtime error?
Reports like https://github.com/intel/bmap-tools/issues/65 make it seem more like the latter.
But I have to read more. But since the zfs_dmu_offset_next_sync setting was disabled by default until recently, I still suspect (but yeah, don't know for sure) that disabling is the safest thing we can currently do on unmodified ZFS systems.
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?
zfs - OpenZFS on Linux and FreeBSD
fzf-fish-integration - 🔍🐟 Fzf plugin for Fish
zfs-issue-15526-check-file
dotfiles - My dotfiles
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption
reflex - Run a command when files change
awesome-rust - A curated list of Rust code and resources.
fzf - :cherry_blossom: A command-line fuzzy finder
whitebox-tools - An advanced geospatial data analysis platform
skim - Fuzzy Finder in rust!
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore