zfs
httm
Our great sponsors
zfs | httm | |
---|---|---|
719 | 98 | |
10,125 | 1,199 | |
1.4% | - | |
9.7 | 9.9 | |
3 days ago | 14 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | 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.
zfs
-
Radxa's SATA HAT makes compact Pi 5 NAS
> The only non-junk PCIe3 option that's even advertised here recently is the overpriced WD Red SN700.
Those WD drives seem to have some real issues, at least with ZFS and btrfs. :(
https://github.com/openzfs/zfs/discussions/14793
- OpenZFS: Fix corruption caused by MMAP flushing problems
- ZFS: Some copied files are still corrupted (chunks replaced by zeros)
-
DiskClick: Ever wanted to hear Old Hard drive sounds
IMO the "next fs" is just zfs. They somewhat recently merged RAIDZ expansion feature https://github.com/openzfs/zfs/pull/12225 and make regular improvements. If no file system has what you need today, zfs will probably be the first one to have it "tomorrow," imo.
- OpenZFS bug reports for native encryption
-
A data corruption bug in OpenZFS?
https://github.com/openzfs/zfs/issues/15526#issuecomment-181...
> zpool get all tank | grep bclone
> kc3000 bcloneused 442M
> kc3000 bclonesaved 1.42G
> kc3000 bcloneratio 4.30x
> My understanding is this: If the result is 0 for both bcloneused and bclonesaved then it's safe to say that you don't have silent corruption.
-
Ask HN: What's your "it's not stupid if it works" story?
A couple years ago, I had an idea for convincing a filesystem to go faster using 2 compression steps instead of one. I couldn't see why it wouldn't work, and I also couldn't convince myself it should.
It seems to have worked out. [1]
[1] - https://github.com/openzfs/zfs/commit/f375b23c026aec00cc9527...
-
ZFS Profiling on Arch Linux
https://github.com/openzfs/zfs/issues/7631
This is a long-standing issue with zvols which affects overall system stability, and has no real solution as of yet.
-
Using ZFS on single disks, combining them with mergerfs, and paritizing them with Snapraid
TIL. Thank you! https://github.com/openzfs/zfs/pull/15022
-
Why does primarycache=metadata reduce my un-cached read speeds?
Difference may be significant, yes https://github.com/openzfs/zfs/pull/14243
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?
zstd - Zstandard - Fast real-time compression algorithm
fzf-fish-integration - 🔍🐟 Fzf plugin for Fish
7-Zip-zstd - 7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard
dotfiles - My dotfiles
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
reflex - Run a command when files change
snapper - Manage filesystem snapshots and allow undo of system modifications
awesome-rust - A curated list of Rust code and resources.
fzf - :cherry_blossom: A command-line fuzzy finder