| To: | Steve Lord <lord@xxxxxxx>, Sean Neakums <sneakums@xxxxxxxx> |
|---|---|
| Subject: | Re: file corruption during emacs build on XFS logical volume |
| From: | Seth Mos <knuffie@xxxxxxxxx> |
| Date: | Fri, 04 Jan 2002 21:26:06 +0100 |
| Cc: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <1010174871.30053.6.camel@jen.americas.sgi.com> |
| References: | <6ug05mj6ah.fsf@zork.zork.net> <1010141444.1992.3.camel@pyewacket> <1010164935.1945.8.camel@UberGeek> <6u666ikn5n.fsf@zork.zork.net> <6usn9mj7id.fsf@zork.zork.net> <6uofkaj6zj.fsf@zork.zork.net> <6ug05mj6ah.fsf@zork.zork.net> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
At 14:07 4-1-2002 -0600, 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. This might explain the fs corruption that some other people saw as well on 2.4.17-xfs. I can't remember who it was, i'll look it up. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. |
| Previous by Date: | Re: file corruption during emacs build on XFS logical volume, Steve Lord |
|---|---|
| Next by Date: | Re: file corruption during emacs build on XFS logical volume, Austin Gonyou |
| Previous by Thread: | Re: file corruption during emacs build on XFS logical volume, Steve Lord |
| Next by Thread: | Re: file corruption during emacs build on XFS logical volume, Austin Gonyou |
| Indexes: | [Date] [Thread] [Top] [All Lists] |