public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Jesper Krogh <jesper@krogh.cc>
Cc: 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: Thu, 1 May 2008 05:15:48 -0700	[thread overview]
Message-ID: <20080501051548.08bbbec1@infradead.org> (raw)
In-Reply-To: <481ACEC4.2040205@krogh.cc>

On Fri, 02 May 2008 10:20:20 +0200
Jesper Krogh <jesper@krogh.cc> wrote:
> Hardware is an Sun Fire X4600 (8xdual-core AMD64 processors). The
> problem seem to be tied to this filesystem. (I cannot havent been able
> to reproduce it on the /-mounted disk of the same system. So if a cpu
> problem.. then it shouldn't be tied to a specific filesystem?
> 
> This is the only activity on the system .. so a load of 1 / 16cpus.

have you run fsck on the filesystem?
(and it might be interesting to use dump the metadata to a file first
to save the broken state for later analysis)

  reply	other threads:[~2008-05-02 10:16 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 [this message]
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
     [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=20080501051548.08bbbec1@infradead.org \
    --to=arjan@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=jesper@krogh.cc \
    --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