[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: Fri, 04 Jan 2002 00:24:29 +0000
In-reply-to: <3C34F294.D6D015BC@xxxxxxxxxx> ("D. Stimits"'s message of "Thu, 03 Jan 2002 17:08:52 -0700")
Mail-followup-to: Linux XFS <linux-xfs@xxxxxxxxxxx>
References: <6u4rm4r53e.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> <6ubsgbq013.fsf@xxxxxxxxxxxxx> <1010069377.23328.15.camel@xxxxxxxxxxxxxxxxxxxx> <1010072382.23328.38.camel@xxxxxxxxxxxxxxxxxxxx> <6u3d1npgx9.fsf@xxxxxxxxxxxxx> <1010075404.12080.79.camel@xxxxxxxxxxxxxxxxxxxx> <1010076426.12080.86.camel@xxxxxxxxxxxxxxxxxxxx> <6uu1u3nt3h.fsf@xxxxxxxxxxxxx> <1010087177.12080.104.camel@xxxxxxxxxxxxxxxxxxxx> <6upu4rnquf.fsf@xxxxxxxxxxxxx> <1010088984.23328.115.camel@xxxxxxxxxxxxxxxxxxxx> <1010097091.23328.117.camel@xxxxxxxxxxxxxxxxxxxx> <6u3d1nnjsc.fsf@xxxxxxxxxxxxx> <3C34F294.D6D015BC@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:
>> begin  Steve Lord quotation:
>> > On Thu, 2002-01-03 at 14:16, Steve Lord wrote:
>> >> On Thu, 2002-01-03 at 14:04, Sean Neakums wrote:
>> >> > You're building emacs 20, though, whose build process may be
>> >> > different from the emacs 21 build process.  There's about three
>> >> > years of development between those two releases.
>> >>
>> >> Yes, I will go back to emacs 21 again, I might be chasing different
>> >> things.
>> >
>> > OK, I was chasing different things, but emacs 21 is building OK for
>> > me on xfs and ext3.
>> This is very weird.  I find it hard to believe that there's
>> something about Debian's packaging that causes the build to fail on
>> XFS *only*.
> Why not find the exact compile line of first failure or first file
> corruption; then run it by hand under strace and see what it says?

After I got that bogus dumped binary, I've done about thirty more
dumps, by hand.  They all seem to run fine, although I'm getting
different md5sums for each of them, even though I'm taking pains to
dump each under the same filename.  I'm not sure if the dumping
process guarantees identical binaries each time or not.

 /////////////////  |                  | 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>