SCIENTIFIC-LINUX-DEVEL Archives

June 2009

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stephan Wiesand <[log in to unmask]>
Reply To:
Date:
Tue, 23 Jun 2009 11:22:15 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (54 lines)
Hi Urs,

On Tue, 2009-06-23 at 11:08 +0200, Urs Beyerle wrote:
> Hi,
> 
> I just spotted a problem on a SL system where the root file system is on xfs. After updating the kernel booting into the
> new kernel failed because the initrd had no xfs support.
> 
> The problem is caused by the fact that "yum update" first updates the kernel and afterwards updates kernel-module-xfs:
> 
> yum update
> ...
> Running Transaction
>   Installing     : kernel                                            [1/8]
> ...
>   Installing     : kernel-module-xfs-2.6.18-128.1.14.el5             [6/8]
> ...
> 
> The mkinitrd script executed by the post install script of the kernel package does not have xfs.ko of the new kernel
> available. Therefore it can not build the new xfs.ko into initrd.
> 
> This can be of course fixed manually by running either
> 
> # yum update
> # /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install 2.6.18-128.1.14.el5
> 
> or
> 
> # yum install kernel-module-xfs-2.6.18-128.1.14.el5
> # yum update
> 
> However, I would like to have it fixed in "yum update".
> 
> Can this be built into the kernel-module yum plugin? Troy?
> 
> Or does anybody see how it can be fixed in the kernel-module-xfs rpm?

I guess you could add a trigger on the kernel rpm and rerun mkinitrd
from that.

Or wait for 5.4 :-)

Cheers,
	Stephan

> Cheers,
> 
> 	Urs
-- 
Stephan Wiesand
  DESY - DV -
  Platanenallee 6
  15738 Zeuthen, Germany

ATOM RSS1 RSS2