From: Jesper Krogh <jesper@krogh.cc>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Ray Lee <ray-lk@madrabbit.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Many open/close on same files yeilds "No such file or directory".
Date: Mon, 05 May 2008 19:54:08 +0200 [thread overview]
Message-ID: <481F49C0.4080001@krogh.cc> (raw)
In-Reply-To: <Pine.LNX.4.64.0805051050350.27703@shark.he.net>
Randy.Dunlap wrote:
> On Mon, 5 May 2008, Jesper Krogh wrote:
>
>> Jesper Krogh wrote:
>>> Ray Lee wrote:
>>>> BTW, I may have missed this earlier, but does it happen *anywhere* on
>>>> the troublesome filesystem (ie, in a newly created subdirectory)?
>>> Yes. It is reproducible on a newly created subdirectory on the
>>> filesystem.
>> Now I've created a new filesystem. (resized the original LVM-volume to half
>> and created a new ext3 one next to it). The problem persists on this new
>> filesystem.
>>
>> Just guessing, can there be something timing related in clearing the FS-cache
>> for the filesystem?
>>
>> Any other suggestions/pointers.
>
> Hi,
>
> Has anyone else been able to reproduce this problem?
No, and out of my systems. I only have this external SCSI-IDE-raid
device I can reproduce it on. The internal system disks doesnt allow me
to reproduce it on the same installation.
--
Jesper Krogh
next prev parent reply other threads:[~2008-05-05 17:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 15:34 Many open/close on same files yeilds "No such file or directory" Jesper Krogh
2008-05-02 5:39 ` Andrew Morton
2008-05-02 8:20 ` Jesper Krogh
2008-05-01 12:15 ` Arjan van de Ven
2008-05-02 11:03 ` Many open/close on same files yeilds Jesper Krogh
2008-05-01 14:07 ` Arjan van de Ven
2008-05-02 15:19 ` Many open/close on same files yeilds "No such file or directory" Jesper Krogh
2008-05-02 15:47 ` Ray Lee
2008-05-02 15:55 ` Jesper Krogh
2008-05-02 16:45 ` Ray Lee
2008-05-02 19:53 ` Jesper Krogh
2008-05-02 19:52 ` Jesper Krogh
2008-05-05 17:43 ` Jesper Krogh
2008-05-05 17:51 ` Randy.Dunlap
2008-05-05 17:54 ` Jesper Krogh [this message]
[not found] ` <2c0942db0805051121r47cc97d2jb71cc8ab9eaa7981@mail.gmail.com>
2008-05-05 18:29 ` Jesper Krogh
[not found] ` <2c0942db0805051154q63a18bcfhce8a30d4a663ea3f@mail.gmail.com>
2008-05-07 20:51 ` Jesper Krogh
2008-05-07 22:27 ` Jesper Krogh
2008-05-02 15:21 ` Jesper Krogh
2008-05-09 5:22 ` Jesper Krogh
2008-05-09 5:36 ` Andrew Morton
2008-05-09 6:09 ` Jesper Krogh
2008-05-09 6:22 ` Andrew Morton
2008-05-12 1:53 ` Neil Brown
2008-05-12 6:00 ` J. Bruce Fields
2008-05-12 6:41 ` Jesper Krogh
2008-05-12 6:51 ` Andrew Morton
[not found] <aoJcW-38V-37@gated-at.bofh.it>
[not found] ` <aoWjI-1Br-5@gated-at.bofh.it>
[not found] ` <aoYOH-6RO-13@gated-at.bofh.it>
[not found] ` <ap5nc-3ZT-7@gated-at.bofh.it>
[not found] ` <ap5Gx-4vu-43@gated-at.bofh.it>
[not found] ` <ap9Ar-4Nn-21@gated-at.bofh.it>
[not found] ` <aqcZe-7Fg-23@gated-at.bofh.it>
[not found] ` <aqd98-7Vb-25@gated-at.bofh.it>
[not found] ` <aqd99-7Vb-27@gated-at.bofh.it>
2008-05-05 19:05 ` Henry Nestler
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=481F49C0.4080001@krogh.cc \
--to=jesper@krogh.cc \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.org \
--cc=rdunlap@xenotime.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox