On Tue, Apr 14, 2009 at 6:20 AM, Jerry Amundson jamundso@gmail.com wrote:
On Mon, Apr 13, 2009 at 5:08 PM, Akemi Yagi amyagi@gmail.com wrote:
I suppose, at some point in time, you had kmod-drbd-xen-8.0.12-1.2.6.18_92.1.6.el5 which installed /lib/modules/2.6.18-92.1.6.el5xen/extra/drbd82/drbd.ko. [expected behavior]
When kmod-drbd82-xen-8.2.6-2 was installed later on, it installed /lib/modules/2.6.18-92.1.13.el5xen/extra/drbd82/drbd.ko and created symlinks through the action of /sbin/weak-modules. Kernels that existed at that moment now point to the drbd.ko in /lib/modules/2.6.18-92.1.13.el5xen. [expected behavior]
Yes, I'm with you so far.
When the kernel was updated to -128 (upon 5.3 update), weak-modules was supposed to do the same (create a symlink to 2.6.18-92.1.13.el5xen). But instead, it made a link to 2.6.18-92.1.6.el5xen. This is the part I don't understand. [???]
It seems related to installation order. With the kernel not yet installed, weak-modules has nothing to pick up in /lib/modules for the new kernel...
[root@xenb ~]# rpm -qa --last | grep xen xen-3.0.3-80.el5_3.2 Mon 13 Apr 2009 01:58:11 PM CDT kernel-xen-2.6.18-128.1.6.el5 Mon 13 Apr 2009 01:57:51 PM CDT xen-libs-3.0.3-80.el5_3.2 Mon 13 Apr 2009 01:57:26 PM CDT kmod-drbd82-xen-8.2.6-2 Thu 19 Mar 2009 02:41:55 PM CDT kernel-xen-2.6.18-92.1.22.el5 Thu 19 Mar 2009 02:41:39 PM CDT kmod-drbd82-xen-8.2.6-1.2.6.18_92.1.10.el5 Fri 15 Aug 2008 03:19:31 PM CDT kernel-xen-2.6.18-92.1.10.el5 Fri 15 Aug 2008 03:19:09 PM CDT
Yes, that is the normal order. /sbin/weak-module is run during the kernel installation as you can see in the script (some messages ago). It surveys installed modules (not kernel built-in) and sets up symlinks for those that are kABI compatible.
When kernel-xen-2.6.18-128.1.6 was installed on your system, it was supposed to make a link to the drbd.ko in /lib/modules/2.6.18-92.1.13.el5xen which already existed at that time. But it didn't. Very strange.
Akemi