Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Thanx Diego, I'll give it a try shortly.
On Thu, 2005-12-08 at 11:01 -0500, Diego Julian Remolina wrote:
> I am attaching my Update notes.
>
> Please note those notes are RHEL4 specific, but they should not be much
> different to what you need to do on suse.
>
> If anybody thinks I should change something on this procedure please let
> me know. I have used it several times with not issues.
>
> If you do not use rpm -Fvh but rather rpm -e old-drbd then rpm -ivh
> new-drbd then be carefull since /etc/drbd.conf gets saved as
> /etc/drbd.conf.rpmsave (at least on RHEL).
>
> Keep your old kernel in place. When installing new kernel, do not use
> rpm -Uvh. Rather use rpm-ivh so that you have both kernels. Since the
> kernel versions are different, the drbd modules will be named different
> and you can have drbd rpms for all kernels installed simultaneously.
>
> If you have any questions about my procedure, e-mail me and I will be
> happy to help.
>
> HTH,
>
> Diego
>
> LLLActive at GMail.com wrote:
> > Hi all,
> >
> > I managed to get DRBD 0.7.14 made and built on my 2.6.13-15-default (#1
> > Tue Sep 13 14:56:15 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux) SUSE 10.0
> > Boxed version. It is running, switches primary and secondary with
> > drbdadm, mounts the primary etc. I'm on to the heartbeat installation
> > now. The second DRBD installation is due next week.
> >
> > Today the update for the 2.6.13-15-default (#1 Tue Sep 13 14:56:15 UTC
> > 2005 x86_64 x86_64 x86_64 GNU/Linux) was announced and installable via
> > YOU.
> >
> > Question: With newbie uncertainty in mind, will it do something to my
> > installation that was made and built (including RPM) on my box. If so,
> > (1) how can I update DRBD for the 'new' Kernel painlessly;
> > (2) if I test the new kernel as it is delivered with the current build
> > of my DRBD, and it strikes, how can I revert back to the old kernel?
> > (not done that yet);
> > (3) Advise me if it is necessary to update the kernel (for the
> > 'stability improvements' and security fixes for the x86_64).
> >
> > All help and advice greatly appreciated.
> >
> plain text document attachment (DRBD-Updating)
> # Created by Diego Julian Remolina
> # Systems Support Specialist III
> # Institute for Bioengineering and Bioscience
> # Georgia Institute of Technology
> # Last edited: 11/16/2005
>
> drbd needs to be updated (re-compiled) everytime a new kernel is installed.
> In order to update drbd you need to follow these steps:
>
> 1. Make sure there were not protocol or api changes so that you can do changes
> in the secondary, then let it sync and then bring the primary down.
>
> ON THE SECONDARY (aragorn):
>
> 2. Update the system so that the new kernels get installed
> up2date -u -f
>
> 3. Extract the sources in /usr/src:
> cd /usr/src
> tar -xzf /path/to/drbd-0.7.14.tar.gz
>
> 4. Find out what the new kernel is so that you can build drbd for that kernel:
> root at aragorn drbd-0.7.14]# ls /usr/src/kernels/
> 2.6.9-22.EL-hugemem-i686 2.6.9-22.EL-i686 2.6.9-22.EL-smp-i686 2.6.9-5.0.5.EL-i686
> Since 2.6.9-22 is the latest kernel, then we want to build the package for the smp
> kernel.
>
> 5. Now you are ready to build for your new kernel:
> make rpm KDIR=/usr/src/kernels/2.6.9-22.0.1.EL-i686
> make rpm KDIR=/usr/src/kernels/2.6.9-22.0.1.EL-smp-i686
>
> 6. Install the rpms located in dist/RPMS/{arch}/
>
> - Stop current drbd
> /etc/init.d/drbd stop
> - Remove module in case is still loaded
> rmmod drbd
> - Remove drbd-OLDVERSION rpms, except the drbd km rpm
> so that you keep the module in case you need to fall
> back to the old kernel
> rpm -Fvh --force dist/RPMS/i386/drbd-*
>
> 7. Reboot the server.
>
> NOW THE PRIMARY
>
> 8. Copy the rpms from the secondary to the primary. DO NOT INSTALL THEM
> YET. /tmp is a good location.
>
> 9. Stop heartbeat on the primary and make sure the secondary took over
> Usually nfs4 needs the /etc/init.d/rpcidmapd restart for the clients
> to keep working.
>
> 10. Update the primary: up2date -u -f
>
> 11. Remove old rpms and install new ones:
> cd /tmp
> rpm -Fvh --force drbd-*.rpm
>
> 13. Reboot the primary and make sure it comes back up and takes over
> correctly.
--
:-)
Al
_________________________________________________
Alemanne
EU