From: Kris Vassallo <kris@linuxcertified.com>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: Stale File handles keep coming back
Date: Wed, 11 May 2005 18:01:34 -0700 [thread overview]
Message-ID: <1115859694.23663.3.camel@localhost.localdomain> (raw)
In-Reply-To: <42786148.1000201@bio.ifi.lmu.de>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
Ok, well I have found very good success in killing this stupid stale
file handle problem in the 2.6.11 kernel by switching from ext3 to ext2
and then rebooting. For the past 5 days not 1 of my developers has
complained about this issue.
Obviously if this machine goes down and a fsck starts running on the 750
GB of data, I am in some deep doo doo, but for now I am using this as a
way of getting around the problem until someone comes up with a nifty
patch.
-Kris
On Tue, 2005-05-03 at 22:44, Frank Steiner wrote:
> Kris Vassallo wrote
>
> > So in reference to this bug
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150759
> > it seems as if ridding the system of the journal by instead using ext2
> > is fixing the problem? I can't tell if that bug has anything to do with
> > providing ESTALE errors but it seems to have the same effect where you
> > can't see files even though they are there.
>
> Yes, sounds very similar...
>
>
> >
> > Has anyone tried using the journal_data_ordered option? I am not sure
> > there is a way to do that in reiser but I know it can be done with ext3.
>
> According to the man page, "data=ordered" is the default. Have you
> explicitely changed it?
>
> I couldn't find any option to change this in reiserfs...
[-- Attachment #2: Type: text/html, Size: 1706 bytes --]
next prev parent reply other threads:[~2005-05-12 1:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 21:07 Stale File handles keep coming back Kris Vassallo
2005-04-26 12:27 ` Neil Brown
2005-04-26 22:22 ` Kris Vassallo
2005-04-27 2:42 ` Neil Brown
2005-04-29 7:01 ` Frank Steiner
2005-04-29 8:00 ` Frank Steiner
2005-04-29 14:08 ` Trond Myklebust
2005-04-30 13:15 ` Frank Steiner
2005-04-30 16:29 ` Trond Myklebust
2005-05-02 6:24 ` Frank Steiner
2005-05-03 10:45 ` Frank Steiner
2005-05-03 11:11 ` Frank Steiner
2005-05-05 0:15 ` Kris Vassallo
2005-05-06 6:38 ` Frank Steiner
2005-05-09 6:04 ` Frank Steiner
2005-04-29 14:03 ` Frank Steiner
2005-05-03 21:21 ` Kris Vassallo
2005-05-04 5:44 ` Frank Steiner
2005-05-04 22:48 ` Kris Vassallo
2005-05-04 23:06 ` Trond Myklebust
2005-05-12 1:01 ` Kris Vassallo [this message]
2005-05-12 1:14 ` Neil Brown
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=1115859694.23663.3.camel@localhost.localdomain \
--to=kris@linuxcertified.com \
--cc=fsteiner-mail@bio.ifi.lmu.de \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.