From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Michael Heyse <mhk@designassembly.de>, linux-kernel@vger.kernel.org
Subject: Re: Reproducible 2.6.11.9 NFS Kernel Crashing Bug!
Date: Thu, 16 Jun 2005 11:10:53 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0506161110280.15642@p34> (raw)
In-Reply-To: <1118933954.2644.8.camel@mindpipe>
On Thu, 16 Jun 2005, Lee Revell wrote:
> On Thu, 2005-06-16 at 05:24 -0400, Justin Piszcz wrote:
>> Alan followed up with me but we did not reach any conclusion as to what
>> was causing it to crash. The main way I got it to crash was dd
>> if=/dev/hde (root drive) of=/nfs/file.img bs=1M, I have not had any issues
>> as far as copying files and such. For you, is it on a particular box or
>> boxes, have you tried copying the other direction? I use NFS over UDP btw
>> (v3).
>>
>> # mount
>> mount:/disk/1 on /remote/1 type nfs
>> (rw,hard,intr,nfsvers=3,addr=192.168.168.253)
>
> Are you both using NFS + software RAID? Is 4KSTACKS enabled?
>
> IIRC people were getting stack overflows with the NFS + RAID + 4K stacks
> combination.
>
> Lee
>
I was not using any type of RAID, SW or HW.
4K stacks was not enabled on either machine.
I am using XFS though.
next prev parent reply other threads:[~2005-06-16 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 13:18 Reproducible 2.6.11.9 NFS Kernel Crashing Bug! Justin Piszcz
2005-05-17 14:47 ` Alan Cox
2005-05-18 0:35 ` Justin Piszcz
2005-05-18 0:36 ` Justin Piszcz
2005-05-18 12:34 ` Peter Staubach
2005-06-16 9:19 ` Michael Heyse
2005-06-16 9:24 ` Justin Piszcz
2005-06-16 14:59 ` Lee Revell
2005-06-16 15:10 ` Justin Piszcz [this message]
2005-06-17 8:12 ` Michael Heyse
2005-06-17 8:11 ` Michael Heyse
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=Pine.LNX.4.63.0506161110280.15642@p34 \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhk@designassembly.de \
--cc=rlrevell@joe-job.com \
/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;
as well as URLs for NNTP newsgroup(s).