Bug#280213: Strange Exim Problem on Alpha

[Steve Langasek]

--EuxKj2iCbKjpUGkD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Nov 08, 2004 at 03:54:59PM -0600, John Goerzen wrote:
> On Mon, Nov 08, 2004 at 01:44:43PM -0800, Steve Langasek wrote:
> > On Mon, Nov 08, 2004 at 02:52:36PM -0600, John Goerzen wrote:
> > > Any help would be appreciated.
> >=20
> > A quick glance at the build logs for exim4 show a large number of warni=
ngs
> > about incorrect integer<->pointer casts.  Have you tried fixing those t=
o see
> > if the problem is in there somewhere?

> Yes, but not in receive.c, which is the file that has the relevant code
> -- which also doesn't call out to any other Exim stuff.

I see from your bug report that this is a reiserfs filesystem.  I've been
told that reiserfs is not considered stable on alpha; it has actually been
disabled in the sarge installer for this architecture over corruption
concerns.  This may or may not be related, but I figured it was worth
pointing out.

The other factor at work here is probably that df is using the statfs()
function from glibc, whereas exim4 is using statfs64() due to the CFLAGS
settings -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE.  We may be looking a=
t a
broken implementation of the statfs64() libc call on alpha, or a broken
statfs64() syscall (either when pointing at reiserfs, or in general).

--=20
Steve Langasek
postmodern programmer

--EuxKj2iCbKjpUGkD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBj/U7KN6ufymYLloRAvz1AKCNSlVqA2SMMqRkqBwz852MBJ3ZQgCdHUXp
NK3uTtf0nZ6dSS5EprvGgiM=
=hRnF
-----END PGP SIGNATURE-----

--EuxKj2iCbKjpUGkD--