kernel-modules-hook VS zfs

I have the opposite feeling. Upgrading kernel requires rebooting, or kernel modules is unable to work. That's annoying. Currently I use kernel-modules-hook to prevent rebooting on Arch.

You can use this pacman hook so that old modules survive a kernel update https://github.com/saber-nyan/kernel-modules-hook

It’s a good idea to reboot ASAP after installing a kernel update anyway, but to keep things running smoothly in the meantime, I recommend installing the kernel-modules-hook package and enabling its systemd service, which keeps the current kernel’s modules available until after the next reboot. (Details here.)

Use https://github.com/saber-nyan/kernel-modules-hook to fix this. It only happens because the package manager completely removes the modules for the current kernel from the filesystem, so you can't load them anymore.

In regards to the “Core parts of the system have been upgraded, a reboot is recommended” notifications, those don’t really mean you need to reboot then. Sometimes I go through two or three minor kernel updates before rebooting my machine. You will rarely encounter things that break without a restart after “core component” updates, and if you install kernel-modules-hook from the repos, the amount of issues you’ll run into after updating will be close to zero. I’ve only encountered this kind of issue once with that package installed, and without it it’s fine too, you’ll just have to reboot if you want to do something like modprobe after a kernel update.

FWIW, kernel-modules-hook is really slow because it depends on rsync, and it rsyncs everytime the hook is fired. https://github.com/saber-nyan/kernel-modules-hook/issues/14 https://github.com/saber-nyan/kernel-modules-hook/pull/15

Thanks for this! I'll switch from kernel-modules-hook and see how it goes.

If you're talking about kernel-modules-hook, haven't you enabled the systemd service to cleanup the old modules as mentioned in the GitHub repo's README?

Be careful if you use ZFS-on-root, make sure not to snapshot bpool or it will brick your system and require a complete reinstall.

https://github.com/openzfs/zfs/issues/13873

> 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

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.

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.

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...

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.

TIL. Thank you! https://github.com/openzfs/zfs/pull/15022