-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
os-prober with many zvols/snapshots makes upgrades painful #62
Comments
There might be a way to avoid patching os-prober because this logic is in the
Installing a dummy test to |
Good call, here's what I'm using now ( #!/bin/sh
# Sub-test to exclude ZVOLs
set -e
partition="$1"
. /usr/share/os-prober/common.sh
if [ "$(stat -L -c %t "$partition")" = "e6" ] ; then
debug "$1 is a ZVOL; skipping"
exit 0
fi
# No ZVOLs found
exit 1 |
When `update-grub` is invoked, `os-prober` tries to mount each zvol node, which is slow on systems with more than a few hundred volumes. Add a device test for `os-prober` that returns early on zvols. Closes: dajhorn/pkg-zfs#62
I added this test and credited you. |
Thanks Darik |
On small change required - this needs to be chmod'd +x |
Thanks. I squeaked it into rc13. |
I store VMs on zvols, and use zfs-auto-snapshot to provde point-in-time rollback. As a result, I current have ~1400 /dev/zd* device nodes. The result is horrendous behaviour from os-prober at kernel/grub update, since it tries to mount them all.
My current hack-around is just to patch /usr/bin/os-prober ignore devs with major 230, but I'm open to more sensible options if anyone has any. I do think os-prober is going to need patching though...
The text was updated successfully, but these errors were encountered: