From: Chris Mason <mason@suse.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Oleg Drokin <green@namesys.com>,
Manuel Krause <manuelkrause@netscape.net>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: BTW: 2.4.19-patches-to-come?
Date: 17 May 2002 11:47:33 -0400 [thread overview]
Message-ID: <1021650453.14986.914.camel@tiny> (raw)
In-Reply-To: <200205171736.50971.Dieter.Nuetzel@hamburg.de>
On Fri, 2002-05-17 at 11:36, Dieter Nützel wrote:
> Sorry Oleg, that I jump in, here...
>
> I get from time to time corrupted files (after reboot and replay) which are
> _NOT_ written during/before crash!!!
> It happes during huge C++ compilation of one of my 3D VIS apps.
>
> After reboot I have waste in the original *.cxx files. This is very strange
> and time consuming 'cause I have to remove every broken file by hand and
> recreate it with CVS when the compiler hit it during the next run.
Is this on IDE? With tails turned on? Are all the affected files less
than 16k?
>
> A similar thing happen during kernel compilations.
> When the system crash (due to kernel devel stuff) some *.o or mostly
> .*.o.flags files are broken after replay/reboot. Yes, this time they are
> written before/during crash and rebuild during replay,
This will be taken care of by the data=ordered patches. I'm combining
them with the data logging stuff.
-chris
next prev parent reply other threads:[~2002-05-17 15:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 15:36 BTW: 2.4.19-patches-to-come? Dieter Nützel
2002-05-17 15:47 ` Chris Mason [this message]
2002-05-17 18:20 ` Dieter Nützel
2002-05-17 18:26 ` Dieter Nützel
2002-05-20 13:48 ` Chris Mason
2002-05-17 15:54 ` Oleg Drokin
2002-05-17 17:05 ` Dieter Nützel
2002-05-17 18:28 ` Oleg Drokin
2002-05-17 19:44 ` Dieter Nützel
2002-05-18 5:44 ` Oleg Drokin
2002-05-18 13:18 ` Dieter Nützel
2002-05-18 16:29 ` Oleg Drokin
2002-05-18 21:44 ` Manuel Krause
2002-05-19 9:44 ` Oleg Drokin
2002-05-20 17:28 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 1:15 Manuel Krause
2002-05-07 5:22 ` Oleg Drokin
2002-05-07 14:02 ` Yury Yu. Rupasov
2002-05-07 19:35 ` Manuel Krause
2002-05-08 5:30 ` Oleg Drokin
2002-05-08 13:04 ` Chris Mason
2002-05-08 13:08 ` Oleg Drokin
2002-05-08 13:16 ` Chris Mason
2002-05-08 13:20 ` Oleg Drokin
2002-05-08 13:34 ` Chris Mason
2002-05-17 1:49 ` Manuel Krause
2002-05-17 4:56 ` Oleg Drokin
2002-05-17 9:47 ` Pierre Etchemaite
2002-05-17 9:47 ` Oleg Drokin
2002-05-07 13:52 ` Yury Yu. Rupasov
2002-05-07 20:41 ` Manuel Krause
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1021650453.14986.914.camel@tiny \
--to=mason@suse.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=green@namesys.com \
--cc=manuelkrause@netscape.net \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.