From: Kris Vassallo <kris@linuxcertified.com>
To: Eiwe Lingefors <eiwe@jhu.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: More Stale NFS handles
Date: Wed, 29 Jun 2005 13:28:07 -0700 [thread overview]
Message-ID: <1120076887.8751.34.camel@localhost.localdomain> (raw)
In-Reply-To: <449CA531-2B73-458E-B632-B1E159637115@jhu.edu>
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
On Thu, 2005-06-23 at 13:55, Eiwe Lingefors wrote:
> The server:
> Dell PowerEdge 2850
> 1 x PowerVault 220S 14x300GB SCSI
> Fedora Core 3
> Kernel 2.6.9-1.667smp
> Several exported LVM volumes all formatted with reiserfs v3.6
> So far nothing I have done has helped reduce the amount of stale NFS
> file handles.
Bah! I have the same problem, I've had it for months now. I was about to
build yet another server and use reiserfs but thanks to you I am spared
the agony of finding out it wont work.
>
> I'm not sure what additional information might be helpful. The
> problems I'm having essentially mirror those of others who have
> posted regarding stale NFS handles in the past few months on this
> list. I'm at my wits end after having fought with this problem for
> weeks.
YES YES YES!!! It almost brings a state of insanity with it!! Plus, atop
my insanity I have a group of 30 developers who are complaining about
not being able to do work because of stale file handles.
> Any insight or pointers would be deeply appreciated. I'll be
> happy to provide additional information if needed.
I was using ext3, upgraded to core 3 from core 1 and had the exact same
problems. What did it for me, until someone fixes this problem, was to
turn off journaling (so basically its back to ext2). Since reverting
back to ext 2 the problem has gone away. Now this is going to be a huge
problem if the machine crashes because fscking a 1.5 TB disk array is
going to suck! I experimented with the way the journaling gets done
(data goes to disk first or journal first) and I wasn't able to fix the
problem.
Aaaaaaargh!
I just thought I would share my ongoing battle story, hopefully someone
will figure out what's causing this and will come up with a fix.
-Kris
>
> Thanks,
> Eiwe Lingefors
>
[-- Attachment #2: Type: text/html, Size: 2368 bytes --]
next prev parent reply other threads:[~2005-06-29 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 20:55 More Stale NFS handles Eiwe Lingefors
2005-06-24 5:48 ` Frank Steiner
2005-06-24 6:15 ` Trond Myklebust
2005-06-24 6:47 ` Frank Steiner
2005-06-29 20:28 ` Kris Vassallo [this message]
2005-01-20 16:38 ` NFSv3, 2.6, ext3 and dir_index Tobias Diedrich
2005-03-14 17:22 ` Chip Salzenberg
2005-03-20 21:21 ` Tobias Diedrich
2005-08-13 9:39 ` Tobias Diedrich
2005-06-29 20:50 ` More Stale NFS handles Bill Rugolsky Jr.
2005-06-29 21:04 ` Trond Myklebust
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=1120076887.8751.34.camel@localhost.localdomain \
--to=kris@linuxcertified.com \
--cc=eiwe@jhu.edu \
--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.