From: Oleg Drokin <green@namesys.com>
To: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Catastrophe with mailboxes on ReiserFS
Date: Wed, 9 Oct 2002 18:31:41 +0400 [thread overview]
Message-ID: <20021009183141.A4778@namesys.com> (raw)
In-Reply-To: <200210091620.15077.Dieter.Nuetzel@hamburg.de>
Hello!
On Wed, Oct 09, 2002 at 04:20:15PM +0200, Dieter N?tzel wrote:
> > What's "it"? Is it means what I describe, or "it" means wrong stuff in the
> > middle of files?
> Wrong stuff in the middle (appended) _AND_ sometimes whole broken files (if
> the files are smaller).
If the damaged part is still within appended datam, it is still possible that
not all of data happened to flush.
> > It only confirms my version, note how whole block of zeroes
> > was inserted after emergency sync (perhaps during crash).
> "whole block of zeroes" would be fine but it isn't sometimes...
> Sometimes it is stuff from other (deleted?) files.
Well, it depend on what was in newly allocated blocks, it might be zeroes for
empty blocks or some deleted data for previously used blocks.
> When I get the "next" crash during kernel compilation I "save" some files for
> you.
Hm. This is not necessary, I know what's happening in your case it seems.
Bye,
Oleg
next prev parent reply other threads:[~2002-10-09 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 20:55 Catastrophe with mailboxes on ReiserFS Robert Tiismus
2002-10-09 5:42 ` Oleg Drokin
2002-10-09 8:06 ` Robert Tiismus
2002-10-09 8:18 ` Oleg Drokin
2002-10-09 14:02 ` Dieter Nützel
2002-10-09 14:09 ` Oleg Drokin
2002-10-09 14:20 ` Dieter Nützel
2002-10-09 14:31 ` Oleg Drokin [this message]
2002-10-09 14:23 ` Dieter Nützel
2002-10-09 14:32 ` Oleg Drokin
2002-10-09 15:15 ` Dieter Nützel
2002-10-09 15:19 ` Oleg Drokin
2002-10-09 15:26 ` Dieter Nützel
2002-10-09 14:10 ` Dieter Nützel
2002-10-09 23:07 ` Matthias Andree
2002-10-10 11:58 ` Newsmail
2002-10-10 11:25 ` Matthias Andree
2002-10-09 11:24 ` Hans Reiser
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=20021009183141.A4778@namesys.com \
--to=green@namesys.com \
--cc=Dieter.Nuetzel@hamburg.de \
--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.