From: Chris Wedgwood <cw@f00f.org>
To: Timo Sirainen <tss@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: readdir loses renamed files
Date: Mon, 25 Oct 2004 01:29:10 -0700 [thread overview]
Message-ID: <20041025082910.GA17089@taniwha.stupidest.org> (raw)
In-Reply-To: <431547F9-2624-11D9-8AC3-000393CC2E90@iki.fi>
On Mon, Oct 25, 2004 at 04:21:57AM +0300, Timo Sirainen wrote:
> My problem is that mails in a large maildir get temporarily
> lost. This happens because readdir() never returns a file which was
> just rename()d by another process. Either new or the old name would
> have been fine, but it's not returned at all.
i don't think there are well defined semantics for this, it's
intrinsically hard to make it work the way you want for a number of
reasons (and what they are depends on the underlying fs)
> Is there a chance this could get fixed? Every OS/filesystem I've
> tested so far has had the same problem
i'll argue it's an application bug
> so I'll have to implement some extra locking anyway (so much for
> maildir being lockless), but it would be nice to have at least one
> OS where it works without the extra locking overhead.
why do you need extra locking? the next time the maildir is scanned
the message(s) will appear surely?
next prev parent reply other threads:[~2004-10-25 8:30 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 [this message]
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
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=20041025082910.GA17089@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tss@iki.fi \
/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
all inboxes | Powered by JetHome®