[Top] [All Lists]

Re: file corruption during emacs build on XFS logical volume

To: Linux XFS <linux-xfs@xxxxxxxxxxx>
Subject: Re: file corruption during emacs build on XFS logical volume
From: Sean Neakums <sneakums@xxxxxxxx>
Date: Thu, 03 Jan 2002 09:03:20 +0000
In-reply-to: <3C33AF81.AC235AD0@xxxxxxxxxx> ("D. Stimits"'s message of "Wed, 02 Jan 2002 18:10:25 -0700")
Mail-followup-to: Linux XFS <linux-xfs@xxxxxxxxxxx>
References: <6u4rm4r53e.fsf@xxxxxxxxxxxxx> <1009995505.14223.9.camel@xxxxxxxxxxxxxxxxxxxx> <6uy9jgpn2x.fsf@xxxxxxxxxxxxx> <6uu1u4pf48.fsf@xxxxxxxxxxxxx> <1010013019.1281.6.camel@xxxxxxxxxxxxxxxxxxxx> <6upu4spccv.fsf@xxxxxxxxxxxxx> <1010013997.1315.11.camel@xxxxxxxxxxxxxxxxxxxx> <6ulmfgpau5.fsf@xxxxxxxxxxxxx> <6uheq4p9ny.fsf@xxxxxxxxxxxxx> <3C33AF81.AC235AD0@xxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i386-debian-linux-gnu)
begin  D. Stimits quotation:

> Sean Neakums wrote:
>> I've been unpacking the source fresh for each try.
> FYI, file compression is extremely sensitive to marginal ram. If
> unpacking has anything to do with it at all, and not the source of
> the unpack or destination, you should double-check ram with
> memtest86 or something similar. Let it run for many hours.

I ran two passes of memtest-86 a few days ago, after I had that XFS
filesystem shutdown.

I'm not getting any errors at the unpack stage.  I mentioned that I
was unpacking fresh for each try in order to establish that the tree
itself was not b0rked.  Note from my previous messages that the builds
have only failed when I built on XFS, and not when I built on ext2,
and that builds on XFS have succeeded when I use 2.4.14-pre7.  This
just doesn't feel random to me.

 /////////////////  |                  | The spark of a pin
<sneakums@xxxxxxxx> |  (require 'gnu)  | dropping, falling feather-like.
 \\\\\\\\\\\\\\\\\  |                  | There is too much noise.

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