[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Strange Exim Problem on Alpha

Le lundi 08 novembre 2004 à 14:37 -0800, Steve Langasek a écrit :
> 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.
> > > 
> > > A quick glance at the build logs for exim4 show a large number of warnings
> > > about incorrect integer<->pointer casts.  Have you tried fixing those to 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.
I can confirm that I did notice filesystem corruptions and lockups on an
Alpha running Woody (with 2.4 kernel) some (2) years ago. Everything
went back to normal when I changed the partition to ext3.

> 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=64 -D_LARGEFILE_SOURCE.  We may be looking at a
> broken implementation of the statfs64() libc call on alpha, or a broken
> statfs64() syscall (either when pointing at reiserfs, or in general).

Reply to: