From: Mirar <mirar-yg@mirar.org>
To: berthiaume_wayne@emc.com
Cc: Dieter.Nuetzel@hamburg.de, reiserfs-list@namesys.com
Subject: Re: power loss -> corruption
Date: 08 May 2003 14:32:53 +0200 [thread overview]
Message-ID: <m1bryd1uve.fsf@orchid.mirar.org> (raw)
In-Reply-To: <93F527C91A6ED411AFE10050040665D007AA853B@corpusmx1.us.dg.com>
berthiaume_wayne@emc.com writes:
> "data=journal" will also work. You'll need to use the data logging
> patches that Chris Mason has put together.
Thanks.
I assume it's the ones I found here?
ftp://ftp.suse.com/pub/people/mason/patches/data-logging/2.4.20
Do I need all of them or just 03-data-logging?
Any reason why they haven't entered the official 2.4.21 (or have they)?
/Mirar
next prev parent reply other threads:[~2003-05-08 12:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 12:23 power loss -> corruption berthiaume_wayne
2003-05-08 12:32 ` Mirar [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 22:38 Anders Widman
2003-05-08 19:37 Fong Vang
2003-05-08 19:52 ` Hans Reiser
2003-03-11 5:15 How to work around bad blocks? Dirk Leber
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
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
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=m1bryd1uve.fsf@orchid.mirar.org \
--to=mirar-yg@mirar.org \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=berthiaume_wayne@emc.com \
--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.