From: Hans Reiser <reiser@namesys.com>
To: Mike Hodson <mike@mystica.cx>
Cc: reiserfs-list@namesys.com, vs@namesys.com,
Oleg Drokin <green@namesys.com>
Subject: Re: Corrupted/unreadable journal: reiser vs. ext3
Date: Wed, 12 Feb 2003 00:58:53 +0300 [thread overview]
Message-ID: <3E49721D.9060205@namesys.com> (raw)
In-Reply-To: <20030211144144.A5A9.MIKE@mystica.cx>
Mike Hodson wrote:
>After this I completely re-checked the drive with Maxtor's disk tools
>disk, and it showed that the drive was 'certified error-free'.
>
This does not mean that there were no bad blocks that were remapped,
does it?
If you have data corruption that we can analyze, please contact us.
We believe that our current release is very stable. We have one known
bug relating to unlink we are still working on, fsck still gets bug
reports, all the linux journaling filesystems have trouble with write
caching being turned on (this is being fixed in the latest 2.5 kernel,
and some have argued over whether it is a bug or a lack of a feature)
because they don't know how to flush disk caches on commit, and other
than that we simply aren't getting bug reports for V3 in 2.4 (oleg's
write performance improvements have gotten some bug reports, but those
aren't in the stable kernel yet).
Oleg and Vladimir, what is the status of the unlink bug? I'd prefer to
say that we have no bugs at all....
--
Hans
next prev parent reply other threads:[~2003-02-11 21:58 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 18:59 Corrupted/unreadable journal: reiser vs. ext3 Dirk Schenkewitz
2003-02-11 20:27 ` Hans Reiser
2003-02-11 21:30 ` Mike Hodson
2003-02-11 21:47 ` Hans Reiser
2003-02-11 21:58 ` Hans Reiser [this message]
2003-02-12 6:35 ` Oleg Drokin
2003-02-11 23:11 ` Adam Goryachev
2003-02-11 23:17 ` Anders Widman
2003-02-12 0:12 ` Hans Reiser
2003-02-12 10:23 ` Anders Widman
2003-02-12 10:47 ` Hans Reiser
2003-02-12 11:12 ` Adam Goryachev
2003-02-12 13:42 ` Anders Widman
2003-02-12 14:15 ` Russell Coker
2003-02-12 15:26 ` Anders Widman
2003-02-12 16:22 ` bscott
2003-02-12 16:28 ` Russell Coker
2003-02-12 16:40 ` Anders Widman
2003-02-13 3:42 ` Zygo Blaxell
2003-02-13 10:13 ` Anders Widman
2003-02-13 14:44 ` Rudy Zijlstra
2003-02-13 3:31 ` Zygo Blaxell
[not found] ` <20030213113003.7ee7af6e.philippe.gramoulle@mmania.com>
2003-02-13 18:17 ` rijndael loopback encryption was [Re: Corrupted/unreadable journal: reiser vs. ext3] Zygo Blaxell
2003-02-12 16:39 ` Corrupted/unreadable journal: reiser vs. ext3 Sam Vilain
2003-02-12 5:12 ` Ross Vandegrift
2003-02-12 7:17 ` Oleg Drokin
2003-02-12 10:17 ` Alexander Lyamin
2003-02-12 10:19 ` Alexander Lyamin
2003-02-12 16:25 ` Vitaly Fertman
2003-02-12 16:56 ` Anders Widman
2003-02-12 17:13 ` Oleg Drokin
2003-02-12 1:02 ` Mike Hodson
2003-02-12 7:25 ` Oleg Drokin
2003-02-12 9:45 ` Hans Reiser
2003-02-12 16:09 ` Sam Vilain
2003-02-12 10:11 ` trolling Alexander Lyamin
2003-02-12 12:32 ` trolling Dirk Schenkewitz
2003-02-12 14:48 ` trolling Chris Mason
2003-02-13 19:54 ` trolling Zygo Blaxell
-- strict thread matches above, loose matches on Subject: below --
2003-02-11 19:43 Corrupted/unreadable journal: reiser vs. ext3 berthiaume_wayne
2003-02-12 10:48 ` Dirk Schenkewitz
2003-02-12 10:59 ` Hans Reiser
2003-02-12 11:24 ` Frank Baumgart
2003-02-12 11:35 ` Stefan Traby
2003-02-12 11:54 ` Dirk Schenkewitz
2003-02-12 12:42 ` Hans Reiser
2003-02-12 13:25 ` Dirk Schenkewitz
2003-02-12 16:22 ` Sam Vilain
2003-02-12 16:53 ` Anders Widman
2003-02-12 17:19 ` Hans Reiser
2003-02-12 17:40 ` Anders Widman
2003-02-12 18:15 ` Dirk Mueller
2003-02-12 18:20 ` Anders Widman
2003-02-12 18:20 ` Chris Dukes
2003-02-13 20:08 ` Zygo Blaxell
2003-02-12 18:27 Anders Widman
2003-02-12 20:05 Dirk Schenkewitz
2003-02-13 22:49 ` Zygo Blaxell
2003-02-14 0:32 ` Hans Reiser
2003-02-14 8:18 ` Oleg Drokin
2003-02-14 10:13 ` Andreas Dilger
2003-02-14 10:17 ` Oleg Drokin
2003-02-14 10:50 ` Andreas Dilger
2003-02-14 10:59 ` Oleg Drokin
2003-02-14 13:34 ` Hans Reiser
2003-02-14 16:04 ` Rudy Zijlstra
2003-02-14 19:06 ` Andreas Dilger
2003-02-14 19:19 ` Hans Reiser
2003-02-15 12:51 ` Vitaly Fertman
2003-02-15 13:00 ` Vitaly Fertman
2003-02-18 19:50 ` Hans Reiser
2003-02-18 20:05 ` Vitaly Fertman
2003-02-18 22:18 ` Hans Reiser
2003-02-15 13:04 ` Anders Widman
2003-02-15 13:23 ` Oleg Drokin
2003-02-17 19:43 ` Hans Reiser
2003-02-15 22:37 ` Andreas Dilger
2003-02-18 18:21 ` Hans Reiser
2003-02-18 19:22 ` Oleg Drokin
2003-02-18 19:28 ` Hans Reiser
2003-02-18 21:17 ` Valdis.Kletnieks
2003-02-18 22:02 ` Matthias Andree
2003-02-19 6:26 ` Oleg Drokin
2003-02-18 22:23 ` Hans Reiser
2003-02-12 20:57 Dirk Schenkewitz
2003-02-14 0:16 Sam Vilain
2003-02-23 23:10 ` Zygo Blaxell
2003-02-14 0:17 Sam Vilain
2003-02-14 0:18 Sam Vilain
2003-02-23 23:31 ` Zygo Blaxell
2003-02-24 1:14 ` Anders Widman
2003-02-14 14:20 Dirk Schenkewitz
2003-02-14 20:58 ` Valdis.Kletnieks
2003-02-14 14:30 Dirk Schenkewitz
2003-02-17 10:04 Dirk Schenkewitz
2003-02-20 1:27 ` Juan Quintela
2003-02-20 9:03 ` Anders Widman
2003-02-20 9:55 Dirk Schenkewitz
2003-02-20 10:20 ` 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=3E49721D.9060205@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=mike@mystica.cx \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.