[Top] [All Lists]

Re: file corruption during emacs build on XFS logical volume

To: Steve Lord <lord@xxxxxxx>
Subject: Re: file corruption during emacs build on XFS logical volume
From: Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Date: 04 Jan 2002 14:29:53 -0600
Cc: Sean Neakums <sneakums@xxxxxxxx>, Linux XFS <linux-xfs@xxxxxxxxxxx>
In-reply-to: <1010174871.30053.6.camel@xxxxxxxxxxxxxxxxxxxx>
References: <1010174871.30053.6.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
What is the affected version with this? 2.4.17 or all?

On Fri, 2002-01-04 at 14:07, Steve Lord wrote:
> On Fri, 2002-01-04 at 12:54, Sean Neakums wrote:
> > begin  Sean Neakums quotation:
> > 
> > > I am now going to do a build of the upstream source and see if I can
> > > make the dump break on that too.  I'm hopeful that it will, as the
> > > unexec code is the same in upstream as in the Debian emacs21
> > > package.
> > 
> > Yep, I just got me a dumped emacs binary full of NULs with the
> > original GNU source.
> OK, bingo, I can replicate this now, I too have a bad binary, it looks
> like the memory is getting reclaimed without getting flushed out to
> disk - which is not good at all.
> This actually gives me something to go on, hopefully it won't take too
> long to find now. Thanks for your persistance in generating a test
> case here.
> Steve
> -- 
> Steve Lord                                      voice: +1-651-683-3511
> Principal Engineer, Filesystem Software         email: lord@xxxxxxx
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@xxxxxxxxxxxxxxx

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb

Attachment: signature.asc
Description: This is a digitally signed message part

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