From: Hans Reiser <reiser@namesys.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Timo Sirainen <tss@iki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: readdir loses renamed files
Date: Fri, 29 Oct 2004 14:15:43 -0700 [thread overview]
Message-ID: <4182B2FF.9040902@namesys.com> (raw)
In-Reply-To: <20041028114413.GL1343@schnapps.adilger.int>
Andreas Dilger wrote:
>On Oct 28, 2004 11:34 +0200, Matthias Andree wrote:
>
>
>>On Mon, 25 Oct 2004, Theodore Ts'o wrote:
>>
>>
>>>And that's because there's no good way to do this without trashing the
>>>performance of the system, especially when most applications don't
>>>care. (Do you really want your entire system running significantly
>>>slower, penalizing all other applications on your system, just because
>>>of one stupid/badly-written application?)
>>>
>>>
>>Please - is it really necessary that application writers are offended in
>>this way? Timo is investing enormous time and effort in writing a *good*
>>application, and he's effectively seeking a way to *robustly* deal with
>>Maildir format mail storage. Please leave it at "readdir/getdents don't
>>work the way you expect and cannot for this and that reason."
>>
>>Timo tries to implement a *robust* Maildir reader and has just bumped
>>into the flaws of DJB's "no-locking" store.
>>
>>Yes, it's a mail server again that poses file system questions on this
>>list; only it's IMAP this time rather than SMTP and directory
>>synchronous I/O...
>>
>>
Matthias is right. readdir is badly architected, and no one has fixed
it for ~30 years.
It should be possible to perform an atomic readdir if that is what you
want to do and if you have space in your process to stuff the result.
Hans
next prev parent reply other threads:[~2004-10-29 21:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 1:21 readdir loses renamed files Timo Sirainen
2004-10-25 8:29 ` Chris Wedgwood
2004-10-25 12:35 ` Timo Sirainen
2004-10-25 12:47 ` Jan Engelhardt
2004-10-25 12:37 ` Theodore Ts'o
2004-10-25 13:22 ` Timo Sirainen
2004-10-28 9:34 ` Matthias Andree
2004-10-28 11:44 ` Andreas Dilger
2004-10-28 14:34 ` Jan Engelhardt
2004-10-28 15:41 ` Matthias Andree
2004-10-29 21:15 ` Hans Reiser [this message]
2004-10-29 21:28 ` Jan Engelhardt
2004-10-30 19:11 ` Hans Reiser
2004-10-31 6:32 ` Jan Engelhardt
2004-11-01 5:38 ` Hans Reiser
2004-10-28 17:06 ` Theodore Ts'o
2004-10-28 19:00 ` Bernd Eckenfels
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=4182B2FF.9040902@namesys.com \
--to=reiser@namesys.com \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tss@iki.fi \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).