From: Chris Dukes <pakrat@www.uk.linux.org>
To: Hans Reiser <reiser@namesys.com>
Cc: Spam <spam@tnonline.net>, reiserfs-list@namesys.com
Subject: Re: Congratulations! we have got hash function screwed up
Date: Fri, 7 Jan 2005 17:28:04 +0000 [thread overview]
Message-ID: <20050107172804.GI18173@ZenIV.linux.org.uk> (raw)
In-Reply-To: <41DEC53A.40403@namesys.com>
On Fri, Jan 07, 2005 at 09:22:02AM -0800, Hans Reiser wrote:
> Chris Dukes wrote:
>
> >
> >
> >All filesystems will fail or suffer degraded performance under
> >certain conditions, you need to determine what conditions are acceptable
> >for your data.
> >
> >
> >
> and each generation of software reduces the extent of such conditions.
> Reiser4 fixes this problem cleanly.
Should reduce. I currently have the misfortune of supporting
some software that seems to be of the "For every bug fixed atleast
one bug with an equal level of impact is introduced" variety.
--
Chris Dukes
hello stacklimit my old friend, I've come to visit you again
next prev parent reply other threads:[~2005-01-07 17:28 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 22:12 Congratulations! we have got hash function screwed up Lehmann
2004-12-29 18:55 ` Stefan Traby
2004-12-29 21:04 ` Lehmann
2004-12-29 21:05 ` Hans Reiser
2004-12-29 21:43 ` Lehmann
2004-12-29 21:46 ` Christian Iversen
2004-12-29 22:27 ` Lehmann
2004-12-30 2:05 ` Hans Reiser
2004-12-30 10:22 ` Matthias Andree
2004-12-30 17:02 ` Lehmann
2005-01-06 12:45 ` Alex Zarochentsev
2005-01-06 14:27 ` Lehmann
2005-01-06 15:56 ` Hans Reiser
2005-01-06 16:13 ` Spam
2005-01-06 16:26 ` Chris Dukes
2005-01-06 16:29 ` Spam
2005-01-06 16:56 ` Chris Dukes
2005-01-07 17:22 ` Hans Reiser
2005-01-07 17:28 ` Chris Dukes [this message]
2005-01-07 23:27 ` flush earlier? (was Re: Congratulations! we have got hash function screwed up) David Masover
2005-01-07 23:52 ` Hans Reiser
2005-01-08 5:03 ` David Masover
2005-01-08 20:48 ` Hans Reiser
2005-01-09 23:26 ` David Masover
2005-01-06 18:55 ` Congratulations! we have got hash function screwed up Edward Shishkin
2005-01-07 17:26 ` Lehmann
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 11:52 Yiannis Mavroukakis
2004-12-30 12:40 ` Matthias Andree
2004-12-30 12:59 ` Cal
2004-12-30 14:18 ` Matthias Andree
2004-12-30 16:40 ` Hans Reiser
2004-12-30 16:51 ` Matthias Andree
2005-01-18 21:17 ` Grzegorz Jaśkiewicz
2005-01-19 16:06 ` Hans Reiser
2005-01-19 22:41 ` David Masover
2005-01-20 13:18 ` Edward Shishkin
2005-01-20 23:43 ` Grzegorz Jaśkiewicz
2005-01-21 9:31 ` Edward Shishkin
2004-12-30 17:07 ` Esben Stien
2004-12-30 17:15 ` Christian Iversen
2004-12-30 17:47 ` Sander
2004-12-30 17:59 ` Esben Stien
2004-12-30 18:30 ` Sander
2004-12-30 18:46 ` Esben Stien
2004-12-30 18:49 ` Chris Dukes
2004-12-30 19:21 ` Sander
2004-12-30 19:29 ` Esben Stien
2004-12-30 18:16 ` Esben Stien
2004-12-30 18:26 ` Spam
2004-12-30 20:41 ` Tom Vier
2004-12-30 23:14 ` Matthias Andree
2004-12-30 23:25 ` Spam
2004-12-31 4:11 ` Hans Reiser
2004-12-31 8:36 ` Matthias Andree
2004-12-30 20:08 ` Hans Reiser
2004-12-30 21:55 ` Esben Stien
2004-12-31 4:05 ` David Masover
2004-12-31 4:26 ` Hans Reiser
2004-12-31 5:59 ` David Masover
2004-12-30 20:57 ` Adrian Ulrich
2004-12-30 21:01 ` Stefan Traby
2004-12-30 21:20 ` brianmas
2004-12-30 17:09 ` Lehmann
2004-12-30 20:11 ` Hans Reiser
2004-12-30 13:24 Yiannis Mavroukakis
2004-12-30 14:11 ` Matthias Andree
2004-12-30 17:22 Yiannis Mavroukakis
2004-12-30 18:16 Burnes, James
2004-12-30 18:36 ` Esben Stien
2004-12-30 19:26 ` Matthias Andree
2004-12-30 19:24 ` Matthias Andree
2004-12-30 20:25 ` 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=20050107172804.GI18173@ZenIV.linux.org.uk \
--to=pakrat@www.uk.linux.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=spam@tnonline.net \
/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.