[Sks-devel] [Fwd: Re: 2.6.x breaks some Berkeley/Sleepycat DB functionality]

[Dan Egli]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just got this back from the Kernel list on the problem I mentioned on
the 2.6 Linux kernels. Might this be of help in determining the best fix?

- --- Dan
- -------- Original Message --------
Subject: Re: 2.6.x breaks some Berkeley/Sleepycat DB functionality
Date: Mon, 12 Jan 2004 18:24:12 +0100
From: Arjan van de Ven <address@hidden>
Reply-To: address@hidden
Organization: Red Hat, Inc.
To: Dan Egli <address@hidden>
CC: address@hidden
References: <address@hidden>

On Mon, 2004-01-12 at 18:16, Dan Egli wrote:
| -----BEGIN PGP SIGNED MESSAGE-----
| Hash: SHA1
|
| I have encountered a strange issue in 2.6.0 and 2.6.1
|
| I run a PGP Public key server on this machine and under 2.4.x it's
| "smooth as silk". But if I boot under 2.6.x, it's gaurenteed failure. If
| I try to build a database using the build command (this is an sks
| server, so it's sks build or sks fastbuild) I IMMEDIATELY get  Bdb
| error. But the exact same command with the exact same libraries and
| input files under 2.4.20 works without a hitch.
|
| Anyone got any ideas? Anything else I can provide to assist in debugging?

this might be the same issue that hit some rpm versions; some versions
of db4 seem to detect the O_DIRECT header presence and starts using
O_DIRECT, without honoring the alignment requirements linux puts on
O_DIRECT usage...


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAAvJBtwT22Jak4/4RAq5JAKDfjY11SXSI1EFF7g12por4rk3BXACg3kNG
7bYE1MuV/UPSsVSKYqbAgCY=
=sS39
-----END PGP SIGNATURE-----