Re: TESTING - yum update for SL5
Testing has been successful thus far. We are planning on pushing this out next Tuesday, December 15, 2009. If you have had any issues with this version of yum, please let me know before then. Thanks Troy Dawson Troy J Dawson wrote: Hello, The kernel module plugin has been updated to deal with the situation where both a package that has a kernel module (such as openafs) is being updated at the same time that a kernel is being updated, while an old kernel is being removed. Two other bugs have been fixed - string TypeError bug - Reported and Fixed by Yannick Perret - negative sack length bug - Reported and Fixed by Tim Rupp To test or update SL5 --- yum --enablerepo=sl-testing update yum or you can download rpm's by hand at http://ftp.scientificlinux.org/linux/scientific/5rolling/testing/i386/yum/ http://ftp.scientificlinux.org/linux/scientific/5rolling/testing/x86_64/yum/ yum-3.2.22-22.sl.noarch.rpm Thanks Troy Dawson -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LSCS/CSI/USS Group __
Re: TESTING - yum update for SL5
As I said in an earlier message, ALL file systems are XFS, /, /boot, and a data partition. Here is the output from the rpm commands: # rpm -q --scripts kernel-2.6.18-128.1.10.el5.x86_64 postinstall scriptlet (using /bin/sh): if [ `uname -i` == "x86_64" -o `uname -i` == "i386" ]; then if [ -f /etc/sysconfig/kernel ]; then /bin/sed -i -e 's/^DEFAULTKERNEL=kernel-smp$/DEFAULTKERNEL=kernel/' /etc/sysconfig/kernel || exit $? fi fi /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install 2.6.18-128.1.10.el5 || exit $? if [ -x /sbin/weak-modules ] then /sbin/weak-modules --add-kernel 2.6.18-128.1.10.el5 || exit $? fi preuninstall scriptlet (using /bin/sh): /sbin/new-kernel-pkg --rminitrd --rmmoddep --remove 2.6.18-128.1.10.el5 || exit $? if [ -x /sbin/weak-modules ] then /sbin/weak-modules --remove-kernel 2.6.18-128.1.10.el5 || exit $? fi # rpm -q --scripts kernel-module-xfs-2.6.18-128.1.10.el5 postinstall scriptlet (using /bin/sh): depmod -a 2.6.18-128.1.10.el5 >/dev/null 2>&1 || : postuninstall scriptlet (using /bin/sh): depmod -a 2.6.18-128.1.10.el5 >/dev/null 2>&1 || : As I said before, do I need to add something someplace to make sure new kernels include XFS in the /boot/initrd* file?
Re: TESTING - yum update for SL5
Hi Brent, Do these machines have XFS as their root filesystem? That would explain what is happening. When you install a kernel, it rebuilds the mkinitrd, while when you install a kernel module, it only does a depmod. To look at the scripts do a rpm -q --scripts like rpm -q --scripts kernel or rpm -q --scripts kernel-module-xfs-2.6.18-128.1.10.el5 Troy Brent L. Bates wrote: Still no joy. I uninstalled: kernel-2.6.18-128.1.10.el5.x86_64 kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64 rebooted into old kernel. Did following command: # yum install kernel-2.6.18-128.1.10.el5.x86_64 kernel-devel-2.6.18-128.1.10.el5.x86_64 kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64 After the above finished, I double checked the size of /boot/initrd-2.6.18-128.1.10.el5.img and knew it was too small for things to have worked, but I rebooted anyways. It failed to fully boot as it couldn't mount the XFS file systems. Here is a list of all `yum' RPM's installed: yum-3.2.19-22.sl.noarch yum-aliases-1.1.16-14.el5.noarch yum-autoupdate-1-1.SL.noarch yum-changelog-1.1.16-14.el5.noarch yum-conf-53-1.SL.noarch yum-cron-0.6-3.el5.noarch yum-downloadonly-1.1.16-14.el5.noarch yumex-2.0.3-1.0.el5.noarch yum-filter-data-1.1.16-14.el5.noarch yum-keys-1.1.16-14.el5.noarch yum-kmod-1.1.16-14.el5.noarch yum-list-data-1.1.16-14.el5.noarch yum-merge-conf-1.1.16-14.el5.noarch yum-metadata-parser-1.1.2-2.el5.x86_64 yum-priorities-1.1.16-14.el5.noarch yum-protectbase-1.1.16-14.el5.noarch yum-protect-packages-1.1.16-14.el5.noarch yum-refresh-updatesd-1.1.16-14.el5.noarch yum-security-1.1.16-14.el5.noarch yum-tsflags-1.1.16-14.el5.noarch yum-updatesd-0.9-2.sl.noarch yum-upgrade-helper-1.1.16-14.el5.noarch yum-utils-1.1.16-14.el5.noarch yum-verify-1.1.16-14.el5.noarch If you have any suggestions or need more information, please let me know.
Re: TESTING - yum update for SL5
Still no joy. I uninstalled: kernel-2.6.18-128.1.10.el5.x86_64 kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64 rebooted into old kernel. Did following command: # yum install kernel-2.6.18-128.1.10.el5.x86_64 kernel-devel-2.6.18-128.1.10.el5.x86_64 kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64 After the above finished, I double checked the size of /boot/initrd-2.6.18-128.1.10.el5.img and knew it was too small for things to have worked, but I rebooted anyways. It failed to fully boot as it couldn't mount the XFS file systems. Here is a list of all `yum' RPM's installed: yum-3.2.19-22.sl.noarch yum-aliases-1.1.16-14.el5.noarch yum-autoupdate-1-1.SL.noarch yum-changelog-1.1.16-14.el5.noarch yum-conf-53-1.SL.noarch yum-cron-0.6-3.el5.noarch yum-downloadonly-1.1.16-14.el5.noarch yumex-2.0.3-1.0.el5.noarch yum-filter-data-1.1.16-14.el5.noarch yum-keys-1.1.16-14.el5.noarch yum-kmod-1.1.16-14.el5.noarch yum-list-data-1.1.16-14.el5.noarch yum-merge-conf-1.1.16-14.el5.noarch yum-metadata-parser-1.1.2-2.el5.x86_64 yum-priorities-1.1.16-14.el5.noarch yum-protectbase-1.1.16-14.el5.noarch yum-protect-packages-1.1.16-14.el5.noarch yum-refresh-updatesd-1.1.16-14.el5.noarch yum-security-1.1.16-14.el5.noarch yum-tsflags-1.1.16-14.el5.noarch yum-updatesd-0.9-2.sl.noarch yum-upgrade-helper-1.1.16-14.el5.noarch yum-utils-1.1.16-14.el5.noarch yum-verify-1.1.16-14.el5.noarch If you have any suggestions or need more information, please let me know.
Re: TESTING - yum update for SL5
Oh! I thought yumex was just a front end to yum and that updating yum would also update yumex. Sorry for the confusion, I didn't realize they were not fully connected. I'll try using just yum to see how that works.
Re: TESTING - yum update for SL5
Brent L. Bates wrote: No joy in Mudville. I started up yumex. Enabled `sl-testing' and installed the latest yum update. After that was finished, I then uninstalled the lastest kernel update, kernel-2.6.18-128.1.10.el5.x86_64 and the XFS module as well, kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64. That finished and I rebooted the machine into the original kernel, kernel-2.6.18-128.1.1.el5.x86_64. I started up yumex again and installed the lastest kernel and XFS modules again. That finished up. Exited yumex and rebooted. Same as before, could not boot up, didn't like the XFS file system. I had to boot the old kernel run `mkinitrd' and then I could boot from the new kernel. More details. We have 4 drives, each drive has 4 partitions. The first partitions of each drive are mirrored as /boot. Second partitions are swap. 3rd partitions are striped as / and the 4th partitions as a data partition. All file systems are XFS. Am I doing something wrong here? Hi Brent, I'm a little confused. What is the point of updating yum if you are using yumex? Try doing the update without yumex, just using yum. Troy -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LCSI/CSI LMSS Group __
Re: TESTING - yum update for SL5
No joy in Mudville. I started up yumex. Enabled `sl-testing' and installed the latest yum update. After that was finished, I then uninstalled the lastest kernel update, kernel-2.6.18-128.1.10.el5.x86_64 and the XFS module as well, kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64. That finished and I rebooted the machine into the original kernel, kernel-2.6.18-128.1.1.el5.x86_64. I started up yumex again and installed the lastest kernel and XFS modules again. That finished up. Exited yumex and rebooted. Same as before, could not boot up, didn't like the XFS file system. I had to boot the old kernel run `mkinitrd' and then I could boot from the new kernel. More details. We have 4 drives, each drive has 4 partitions. The first partitions of each drive are mirrored as /boot. Second partitions are swap. 3rd partitions are striped as / and the 4th partitions as a data partition. All file systems are XFS. Am I doing something wrong here?
Re: TESTING - yum update for SL5
For the past week, I've been booting into the 2.6.18-128.1.1.el5 kernel. Now, today, after using `mkinitrd', I'm booting into the 2.6.18-128.1.10.el5 kernel. I've rebooted this system fine several times now with the new kernel.
Re: TESTING - yum update for SL5
Which kernel did it actually boot into? -Connie Sieh On Wed, 13 May 2009, Brent L. Bates wrote: I installed the lastest kernel: kernel-2.6.18-128.1.10.el5.x86_64 and XFS module: kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64 on a SL5.3 system. After rebooting, the kernel didn't know anything about XFS, when my previous one still did. I saw Troy's note, so I uninstalled both the kernel and XFS module. I enabled the `sl-testing' repo and updated yum. I then proceeded to install both of the above packages again. I rebooted and the new kernel still didn't know anything about XFS. Shouldn't the XFS module been automatically included in the new `initrd' file? Did I do something out of order or wrong? I want to make sure this doesn't happen again. I manually ran the `mkinitrd' command and now the system boots fine with the new kernel. -- Brent L. Bates (UNIX Sys. Admin.) M.S. 912 Phone:(757) 865-1400, x204 NASA Langley Research Center FAX:(757) 865-8177 Hampton, Virginia 23681-0001 Email: b.l.ba...@larc.nasa.gov http://www.vigyan.com/~blbates/
Re: TESTING - yum update for SL5
I installed the lastest kernel: kernel-2.6.18-128.1.10.el5.x86_64 and XFS module: kernel-module-xfs-2.6.18-128.1.10.el5-0.4-2.sl5.x86_64 on a SL5.3 system. After rebooting, the kernel didn't know anything about XFS, when my previous one still did. I saw Troy's note, so I uninstalled both the kernel and XFS module. I enabled the `sl-testing' repo and updated yum. I then proceeded to install both of the above packages again. I rebooted and the new kernel still didn't know anything about XFS. Shouldn't the XFS module been automatically included in the new `initrd' file? Did I do something out of order or wrong? I want to make sure this doesn't happen again. I manually ran the `mkinitrd' command and now the system boots fine with the new kernel. -- Brent L. Bates (UNIX Sys. Admin.) M.S. 912 Phone:(757) 865-1400, x204 NASA Langley Research CenterFAX:(757) 865-8177 Hampton, Virginia 23681-0001 Email: b.l.ba...@larc.nasa.govhttp://www.vigyan.com/~blbates/
