Jerry Amundson wrote: > Shall I open a bug? > > [root at app1 ~]# rpm -qa \*drbd\* > kmod-drbd82-xen-8.2.6-2 > drbd82-8.2.6-1.el5.centos > [root at 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 at 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. Of course you know that such update will *stop* your drbd node, right ? (as the kmod will be updated and drbd will see a diff between kmod and userland tools and so will stop itself) . Of course you'll be able to start it up just after the update -- -- Fabian Arrotin idea=`grep -i clue /dev/brain` test -z "$idea" && echo "sorry, init 6 in progress" || sh ./answer.sh