xfs
[Top] [All Lists]

Re: Patch 1300 & rpm issue with 1.3.0

To: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>
Subject: Re: Patch 1300 & rpm issue with 1.3.0
From: Russell Cattelan <cattelan@xxxxxxx>
Date: Tue, 26 Aug 2003 10:43:45 -0500
Cc: Kai Leibrandt <k_leibrandt@xxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <3F4B73F3.1A08113B@ch.sauter-bc.com>
References: <Pine.LNX.4.44.0308241122220.16149-100000@stout.americas.sgi.com> <3F4B73F3.1A08113B@ch.sauter-bc.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Tue, 2003-08-26 at 09:51, Simon Matter wrote:
> Eric Sandeen schrieb:
> > 
> > On Sun, 24 Aug 2003, Kai Leibrandt wrote:
> > 
> > Boy, that's an annoying bug...  it's somewhere in the guts of Red Hat's
> > kernel + nptl patches + O_DIRECT + rpm.  I think that Red Hat will 
> > eventually
> > have a new version of RPM that works with this kernel.  In the meantime,
> > I'd either:
> 
> Hmm, can somebody explain what the patch 1300 problem is? I have built
> my own 2.4.20-20.7.XFS1.3.0 and 2.4.20-20.9.XFS1.3.0 rpms and I'm using
> the 20.7 version on RedHat 7.2 without any problem. Did I miss
> something? Is there a problem when using in on RedHat 9? Of course 20.9
> has the nptl patches so should I expect any problems which are not
> present in 20.7?
Yes, this only shows up with the nptl patch applied, and only the RH9
kernels apply that patch. The same srpm build for a RH7.x or RH8 system 
won't have the nptl patch applied.

The problem appears to be someplace in the db4 code.

> 
> Simon
> 
> > 
> > a) rebuild with patch 1300 in place, if you don't care about using O_DIRECT
> > or
> > b) set up an alias for "rpm" to prefix it with LD_ASSUME_KERNEL=2.2.5
> >
> 


<Prev in Thread] Current Thread [Next in Thread>