On 9/8/09, Fabian Arrotin fabian.arrotin@arrfab.net wrote:

Jerry Amundson wrote:

...

Shall I open a bug?

[root@app1 ~]# rpm -qa *drbd* kmod-drbd82-xen-8.2.6-2 drbd82-8.2.6-1.el5.centos [root@app1 ~]# echo n | yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile

• epel: mirrors.tummy.com
• base: mirror.fdcservers.net
• updates: mirror.unl.edu
• addons: mirrors.tummy.com
• extras: mirrors.liquidweb.com

Excluding Packages in global exclude list Finished Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package drbd83.x86_64 0:8.3.2-6.el5_3 set to be updated --> Finished Dependency Resolution

Dependencies Resolved

================================================================================ Package Arch Version Repository Size ================================================================================ Installing: drbd83 x86_64 8.3.2-6.el5_3 extras 210 k replacing drbd82.x86_64 8.2.6-1.el5.centos

Transaction Summary

Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s)

Total download size: 210 k Is this ok [y/N]: Exiting on user Command Complete! [root@app1 ~]# _______________________________________________

Add a `yum install kmod-drbd83` (or kmod-drbd83-xen) that will normally instead fetch drbd83 as a required dep .. and that will update the current drbd82 that you have on your system.

My point is why does drbd83` have an obsoletes for drbd82, but kmod-drbd83` (or kmod-drbd83-xen) does not??

Or, is that just not the way kmod works?

thanks, jerry

On 9/10/09, Akemi Yagi amyagi@gmail.com wrote:

I think that kmod-drbd82 could / should have been obsoleted by kmod-drbd83. While they can coexist without any conflict, kmod-drbd82 is no longer needed once drbd82 is updated to drbd83. So, uninstalling kmod-drbd82 would make sense.

Umm, didn't I just read that you're part of the team which builds the kmods, so can't you just "make it so"? :-)

Or, back to my original question, should I create a bug report?

Thanks, jerry

On 09/10/2009 10:18 PM, Akemi Yagi wrote:

On Thu, Sep 10, 2009 at 8:04 PM, Jerry Amundson jamundso@gmail.com wrote:

...

On 9/10/09, Akemi Yagi amyagi@gmail.com wrote:

...

I think that kmod-drbd82 could / should have been obsoleted by kmod-drbd83. While they can coexist without any conflict, kmod-drbd82 is no longer needed once drbd82 is updated to drbd83. So, uninstalling kmod-drbd82 would make sense.

Umm, didn't I just read that you're part of the team which builds the kmods, so can't you just "make it so"? :-)

I am part of the ELRepo team.

The drbd kmods are built by the CentOS devs. So ... I am free to find fault with them. :-D :-D

...

Or, back to my original question, should I create a bug report?

Actually, the reason is that kmods are not built in the same way as other packages, they are built buy a stand alone script, that I normally do not like to modify specifically for individual packages.

Also, there is NO conflict or problem having both modules installed.

Also, ALSO :D, I published an article on how to upgrade DRBD here:

http://centosnow.blogspot.com/2009/08/drbd-packages-in-centos-4-and-centos-5...

So, I do not agree that kmod needs to obsolete the older one. I think that having the older kmod there in case you need to boot into the older kernel is not bad.

The only reason that you had a problem is that the OLD KMOD did not run.

I would NEVER, EVER update a DRBD cluster with yum. You need to manipulate heartbeat to keep your services on line while upgrading, etc. etc. I would (and do) want to have the old module installed until everything is working on the new module.

Also, I am fairly sure the old module will work with older kernels while the new module will work with newer kernels regardless of the drbd82 or drbd83 installed (since in CentOS 5, the new module may have requires so that it does not work on older kernels).

On 11/09/2009, Akemi Yagi amyagi@gmail.com wrote:

On Fri, Sep 11, 2009 at 4:46 AM, Johnny Hughes johnny@centos.org wrote:

...

Also, there is NO conflict or problem having both modules installed.

True (as I mentioned in my earlier post). But see below...

...

Also, ALSO :D, I published an article on how to upgrade DRBD here:

http://centosnow.blogspot.com/2009/08/drbd-packages-in-centos-4-and-centos-5...

This is a must-read. You should advertise it in more places. :-D

...

So, I do not agree that kmod needs to obsolete the older one. I think that having the older kmod there in case you need to boot into the older kernel is not bad.

That is the statement I have difficulty understanding. :) In case you need to boot into the older kernel ... the drbd module from -83 should be there as a symlink. Or, if you mean boot into the older kernel to get drbd.ko *82*, then you would have to reinstall drbd82.

In other words, if drbd83 obsoletes drbd82, there is no merit for still having drbd.ko (82) around because drbd82 gets removed upon the 82 -> 83 upgrade. If someone needs to go back to the 82, he needs to manually install drbd82 anyway. (hope I'm making sense here) :-)

One (minor) drawback of keeping both kmods is that each time /sbin/meak-module is run, it has to do extra work going through all installed kernels, once for kmod-drbd82 and another time for kmod-drbd83.

Akemi

• now completely hiding under a huge rock

A question in two parts -- for Akemi to consider:

Are the kmod-drbd* packages kABI tracking? Or are they kernel version dependant?

Alan.

On 11/09/2009, Akemi Yagi amyagi@gmail.com wrote:

On Fri, Sep 11, 2009 at 8:29 AM, Alan Bartlett ajb@elrepo.org wrote:

...

...

One (minor) drawback of keeping both kmods is that each time /sbin/meak-module is run, it has to do extra work going through all installed kernels, once for kmod-drbd82 and another time for kmod-drbd83.

Akemi

• now completely hiding under a huge rock

A question in two parts -- for Akemi to consider:

Are the kmod-drbd* packages kABI tracking? Or are they kernel version dependant?

Alan.

The recent version of kmod-drbd82 is kABI-tracking. kmod-drbd83 is new and is also kABI-tracking.

Hmm. I see. Thanks.

Alan. (Who now wonders if there is space for him to hide behind Akemi's rock . . . )

On 9/11/09, Johnny Hughes johnny@centos.org wrote:

On 09/10/2009 10:18 PM, Akemi Yagi wrote:

...

On Thu, Sep 10, 2009 at 8:04 PM, Jerry Amundson jamundso@gmail.com wrote:

...

On 9/10/09, Akemi Yagi amyagi@gmail.com wrote:

...

I think that kmod-drbd82 could / should have been obsoleted by kmod-drbd83. While they can coexist without any conflict, kmod-drbd82 is no longer needed once drbd82 is updated to drbd83. So, uninstalling kmod-drbd82 would make sense.

Umm, didn't I just read that you're part of the team which builds the kmods, so can't you just "make it so"? :-)

I am part of the ELRepo team.

The drbd kmods are built by the CentOS devs. So ... I am free to find fault with them. :-D :-D

...

Or, back to my original question, should I create a bug report?

Actually, the reason is that kmods are not built in the same way as other packages, they are built buy a stand alone script, that I normally do not like to modify specifically for individual packages.

Also, there is NO conflict or problem having both modules installed.

Also, ALSO :D, I published an article on how to upgrade DRBD here:

http://centosnow.blogspot.com/2009/08/drbd-packages-in-centos-4-and-centos-5...

Good to know. [ btw, typo in 2. s/expect/except/ ]

So, I do not agree that kmod needs to obsolete the older one. I think that having the older kmod there in case you need to boot into the older kernel is not bad.

Fair enough.

The only reason that you had a problem is that the OLD KMOD did not run.

Ahhh, right. I'm still getting bitten by this problem from April[1] where kernel-xen installs break kmod's until I erase/install the kmod.

[1] http://lists.centos.org/pipermail/centos-devel/2009-April/004368.html

I would NEVER, EVER update a DRBD cluster with yum. You need to manipulate heartbeat to keep your services on line while upgrading, etc. etc. I would (and do) want to have the old module installed until everything is working on the new module.

All fine if you need heartbeat, and have the time to go through the 12+ steps in your blog.

Also, I am fairly sure the old module will work with older kernels while the new module will work with newer kernels regardless of the drbd82 or drbd83 installed (since in CentOS 5, the new module may have requires so that it does not work on older kernels).

Yes, I just tested the kmod82/drbd83 combo. There is a warning but it works fine.

Is using drbd on kernel-xen the difference? I'd guess someone must test such a use case, right? Or, because I don't use heartbeat, but do have regular (eg. cron) runs of "yum -y update && reboot" I'm expecting too much?

I realize that sysadmin solutions are never simple, but this seems to add complexity where it's not needed.

also looking for one of those rocks, jerry