public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kim Holviala <kim@holviala.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Spontaneous reboot with 2.6.10 and NFSD
Date: Thu, 10 Feb 2005 11:36:01 +0200	[thread overview]
Message-ID: <420B2B01.5020206@holviala.com> (raw)
In-Reply-To: <16907.10130.293919.399727@cse.unsw.edu.au>

Neil Brown wrote:
> On Thursday February 10, kim@holviala.com wrote:
> 
>>Anyway, I mount the export to a Linux client (tried with a few with 
>>different 2.6 kernels and distros) and then start copying files from 
>>clients CDROM to the server through NFS. After copying a few small 
>>files, the first big one reboots the server.
> 
> Can you be specific about the size of the "big" file?

Well, there were two bigger files, the first 18 megs and the second 35 
megs and the copying never got past those two. But in the end it wasn't 
the size - I was able to make it reboot with a small C source file...

> Also, what filesystem is being used on the server, what mount flags
> (if any) and what export options.

All the files are here:
http://www.holviala.com/~kimmy/crash/mount

Mount options:
/dev/md8 on /boot type ext3 (rw,nosuid,noatime)

I forgot to transfer the exports file, and now the server is dead... 
Will do that later.

> Having some sort of console, whether VGA, serial, or network, to view
> the Oops would be invaluable.

I'll carry the server next to a monitor once I get back home.



Kim

  reply	other threads:[~2005-02-10 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10  7:39 Spontaneous reboot with 2.6.10 and NFSD Kim Holviala
2005-02-10  8:27 ` Kim Holviala
2005-02-10  8:52   ` Kim Holviala
2005-02-10  9:21 ` Neil Brown
2005-02-10  9:36   ` Kim Holviala [this message]
2005-02-10 11:07     ` Kim Holviala

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=420B2B01.5020206@holviala.com \
    --to=kim@holviala.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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