On Fri, Aug 29, 2003 at 09:01:47AM -0500, Steve Lord wrote:
> On Fri, 2003-08-29 at 06:57, Foris, Jim (MED) wrote:
>
> >
> > Turns out that information is in my original posting:
> >
> > 4144 write(2, "write: 0xbffed120, 8192: Invalid"..., 41) = 41
> > <0.000012>
> >
> > So the buffer address, 0xbffed120, is NOT correctly alligned.
> >
> >
> > AND THE MYSTERY IS SOLVED; RPM fails because the person who tried to use
> > O_DIRECT file access to an internal database file did not check
> > for/guarantee
> > correct buffer address alignment. This bug did not show up to Red Hat
> > because
> > they never tested it (RPM) on a file system that actually supports O_DIRECT
> > (because they don't have any).
> >
>
> Can someone bug ;-) redhat about this one then?
Already known problem there. Solution is to hack out O_DIRECT support
in rpm in the specfile. Unfortunately this leaves the tarball itself
with the buggy O_DIRECT calls in place.
See a forward from the rpm-list to this list in a minute.
--
Axel.Thimm@xxxxxxxxxxxxxxxxxxx
pgpaPGAGMJSvc.pgp
Description: PGP signature
|