From: <pcg( Marc)@goof(A.).(Lehmann )com>
To: Yiannis Mavroukakis <yiannis@jaguarfreight.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Congratulations! we have got hash function screwed up
Date: Thu, 30 Dec 2004 18:09:36 +0100 [thread overview]
Message-ID: <20041230170936.GB23354@schmorp.de> (raw)
In-Reply-To: <77912E9FD42896419D1CEF15E1C397A58AFCF1@london.jaguarfreightservices.local>
On Thu, Dec 30, 2004 at 11:52:58AM -0000, Yiannis Mavroukakis <yiannis@jaguarfreight.com> wrote:
> Your "proven" reasoning sounds a bit strange to me..Microsoft (aka major
> distributor at least in my books) had her filesystems "in the field" for
> ages, does this prove any of them good (or bad for that matter)?
You state that "proven" is the same as "good", but why you do so escapes
me. In general, you can easily prove that black == white (etc.) by such
illogical reasoning.
The reasoning in fact is that file systems which are out in the field for
years have _known_ properties, are proven to work with some amount of
software, possibly including software that specicially has workarounds for
filesystem shortcomins (i.e. squid with it's multi-dir-hierarchy, which is
just a workaround for basically all non-reiserfs filesystems, and now also
for reiserfs3 filesystems, which also doesn't cope with millions of files
in a dir, as opposed to the original claims by it's developers).
This is cerftainly true for microsofts filesystems: you know what to expect
from vfat or ntfs, for example.
For new filesystems, the issue is completely different. Look at the "file
is a directory" approach that formerly was the default in reiserfs. This
breaks a number of programs, despite the expectancy by the reiserfs
authors that this is not the case (in my experience, stat "path/." to
quickly check wether sth. is a file or a directory is pretty common). Unless
the filesystem is in the field for some time these bugs will not be found.
--
The choice of a
-----==- _GNU_
----==-- _ generation Marc Lehmann
---==---(_)__ __ ____ __ pcg@goof.com
--==---/ / _ \/ // /\ \/ / http://schmorp.de/
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
next prev parent reply other threads:[~2004-12-30 17:09 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 11:52 Congratulations! we have got hash function screwed up 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 [this message]
2004-12-30 20:11 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
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
2004-12-30 17:22 Yiannis Mavroukakis
2004-12-30 13:24 Yiannis Mavroukakis
2004-12-30 14:11 ` Matthias Andree
2004-12-28 22:12 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
2005-01-06 18:55 ` Edward Shishkin
2005-01-07 17:26 ` Lehmann
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=20041230170936.GB23354@schmorp.de \
--to=pcg@goof.com \
--cc=reiserfs-list@namesys.com \
--cc=yiannis@jaguarfreight.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.