mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Michael Heyse <mhk@designassembly.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reproducible 2.6.11.9 NFS Kernel Crashing Bug!
Date: Thu, 16 Jun 2005 05:24:59 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0506160523190.6459@p34> (raw)
In-Reply-To: <42B14415.5060105@designassembly.de>

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)


On Thu, 16 Jun 2005, Michael Heyse wrote:

> Hi Justin and others,
>
> did you manage to resolve this problem? I'm also experiencing apparantly NFS-related crashes (kernel
> hangs after a couple of seconds up to minutes, no syslog entries, nothing at all works any more)
> using 2.6.11.10 and NFS V3 over TCP, standard r/wsizes, ext3 on a RAID5 array. Is this possibly
> arch- or otherwise hardware-dependent? The NFS server works fine on my P4 on ASUS P4P800 board,
> while it crashes my EPIA Board (VIA C3) using the same software configuration. Other network
> applications run fine (as a workaround I'm using samba right now instead of nfs), so I don't think
> my hardware is broken.
>
> Thanks,
> Michael
>

  reply	other threads:[~2005-06-16  9:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14 13:18 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 [this message]
2005-06-16 14:59     ` Lee Revell
2005-06-16 15:10       ` Justin Piszcz
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.0506160523190.6459@p34 \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhk@designassembly.de \
    /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

all inboxes | Powered by JetHome®