From: "Malte Schröder" <maltesch@gmx.de>
To: "Chakri n" <chakriin5@gmail.com>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: OOPS in shrink_dcache_for_umount
Date: Sat, 4 Aug 2007 12:01:05 +0200 [thread overview]
Message-ID: <20070804120105.47ae82fc@highlander.home.lan> (raw)
In-Reply-To: <92cbf19b0708021427l7c88c642g3901e393ac2b90b9@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 683 bytes --]
On Thu, 2 Aug 2007 14:27:04 -0700
"Chakri n" <chakriin5@gmail.com> wrote:
> Hi,
>
> We are seeing this problem while unmounting file systems. It happens
> once in a while.
> I am able to grab the trace and core from linux-2.6.18-1.8.el5, but I
> have observed the same problem with linux-2.6.20.1 kernel.
>
> Has this problem fixed in recent kernel?
>
I had those too ... but I haven't seen one in a while.
I currently run 2.6.22 + cfs-v19 + the Patch from
http://linux-nfs.org/Linux-2.6.x/2.6.22/linux-2.6.22-NFS_ALL.dif
--
---------------------------------------
Malte Schröder
MalteSch@gmx.de
ICQ# 68121508
---------------------------------------
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-04 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 21:27 OOPS in shrink_dcache_for_umount Chakri n
2007-08-04 10:01 ` Malte Schröder [this message]
2007-08-05 16:39 ` Chakri n
2007-08-06 19:18 ` Chakri n
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=20070804120105.47ae82fc@highlander.home.lan \
--to=maltesch@gmx.de \
--cc=chakriin5@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox