From: Mirar <mirar-yg@mirar.org>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: reiserfs-list@namesys.com
Subject: Re: power loss -> corruption
Date: 08 May 2003 15:19:15 +0200 [thread overview]
Message-ID: <m17k911sq4.fsf@orchid.mirar.org> (raw)
In-Reply-To: <200305081502.47455.Dieter.Nuetzel@hamburg.de>
> Maybe you can preset some corrupted file snippets?
I'll see if I can dig up any good.
But I can give examples, for instance .zsh-history with 65536 bytes of
illicit data inserted in the middle - 65536 bytes of which 63898 comes
from a gtk-gnutella file (downloads, I think) and the remaining 1638
is NUL characters. Both files were corrupted after restart, but
gtk-gnutella ate it's file so I can't check how it looked.
Lots of things like that. The numbers are so even so I would figure
that the wrong blocks get in the wrong files somehow.
/Mirar
next prev parent reply other threads:[~2003-05-08 13:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 5:15 How to work around bad blocks? Dirk Leber
2003-03-10 20:50 ` Anders Widman
2003-05-08 11:18 ` power loss -> corruption Mirar
2003-05-08 11:48 ` Dieter Nützel
2003-05-08 12:06 ` Mirar
2003-05-08 13:02 ` Dieter Nützel
2003-05-08 13:19 ` Mirar [this message]
2003-05-08 13:31 ` Dieter Nützel
2003-05-15 8:40 ` Mirar
2003-05-15 11:23 ` Dieter Nützel
2003-05-15 15:17 ` Mirar
2003-05-08 18:58 ` Hans Reiser
2003-05-08 19:20 ` Mirar
2003-05-08 19:28 ` Hans Reiser
2003-05-08 19:31 ` Hans Reiser
2003-05-08 19:39 ` Mirar
2003-05-08 12:02 ` Bill Rees
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 12:23 berthiaume_wayne
2003-05-08 12:32 ` Mirar
2003-05-08 12:38 ` Marc-Christian Petersen
2003-05-08 12:34 ` Anders Widman
2003-05-08 12:39 ` Marc-Christian Petersen
2003-05-08 13:01 ` Dieter Nützel
2003-05-08 13:24 ` Chris Mason
2003-05-08 13:36 ` Dieter Nützel
2003-05-08 13:40 ` Chris Mason
2003-05-08 12:39 ` Dieter Nützel
2003-05-08 19:37 Fong Vang
2003-05-08 19:52 ` Hans Reiser
2003-05-15 22:38 Anders Widman
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=m17k911sq4.fsf@orchid.mirar.org \
--to=mirar-yg@mirar.org \
--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.