From: Hans Reiser <reiser@namesys.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org, Vladimir Demidov <demidov@namesys.com>
Subject: Re: readdir loses renamed files
Date: Sun, 31 Oct 2004 21:38:36 -0800 [thread overview]
Message-ID: <4185CBDC.6090502@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0410310726060.3581@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>>>>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.
>>>>
>>>>
>>>How much would it cost to always append the new name into the directory rather
>>>than modifying it in place?
>>>
>>>
>>Forgive me, what does the sentence above mean? Paste it out of order?
>>
>>
>
>As I have read from earlier replies, ext2/3 replaces a filename with the new
>one, given that it is the same length or shorter, and especially that might
>skip a while when readdir()ing.
>So I was concerned about the speed impact which would arise, if the filename
>was never modified in-place but always appended as a new object to the
>end-of-directory.
>
>
>
>Jan Engelhardt
>
>
The api is fundamentally broken. Sorry. Will try to avoid making that
mistake in sys_reiser4.
next prev parent reply other threads:[~2004-11-01 5:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 1:21 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
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 [this message]
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=4185CBDC.6090502@namesys.com \
--to=reiser@namesys.com \
--cc=demidov@namesys.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome