https://bugzilla.novell.com/show_bug.cgi?id=851722 https://bugzilla.novell.com/show_bug.cgi?id=851722#c8 James Carter <jimc@math.ucla.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jimc@math.ucla.edu | --- Comment #8 from James Carter <jimc@math.ucla.edu> 2013-12-07 05:46:45 UTC --- Starting with the standard os-prober-1.61-3.1.2.x86_64 and /etc/default/grub saying GRUB_DISABLE_OS_PROBER=false. If I do grub2-mkconfig -o /boot/grub2/grub.cfg syslog shows the volcanic eruption from XFS. I attached the complete performance, which I should have done the first time around. It's the same as in the oss.sgi.com bug report, except slight differences in the call trace because they have kernel 3.7.x while we have 3.11.6. If GRUB_DISABLE_OS_PROBER=true, nothing at all is seen in syslog, as expected. I installed os-prober-1.61-52.1.x86_64.rpm from your repo (and btrfsprogs, snapper, and its dependencies). With GRUB_DISABLE_OS_PROBER=false I did grub2-mkconfig -o /boot/grub2/grub.cfg and the debug messages indicated a much more sane logic in os-prober, and in particular, no XFS involvement at all, and /dev/sda4 (the extended partition) is rejected out of hand. Thank you for this improvement; I'll install it on my other machines. I look forward to seeing it in an official update. Someone with a known corrupt filesystem or with other reasons to not mount it, should be sure to set GRUB_DISABLE_OS_PROBER=true. I still haven't figured out what would have execed grub2-mkconfig so long after booting. Maybe purge-kernels.service, if it does purge a kernel. It has IOSchedulingClass=idle which could have made it start late. It would be nice to only install btrfsprogs and snapper-zypp-plugin if the machine actually had (or gained in the future) a BTRFS partition, but I can't imagine how to do a dynamic dependency of this kind. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.