From: Grant Coady <grant_lkml@dodo.com.au>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Repeatable crash under 2.6.13.2 + NFS
Date: Tue, 27 Sep 2005 19:03:33 +1000 [thread overview]
Message-ID: <u62ij19vjosurf6h3dovph0gcgmp3tdpth@4ax.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0509270429360.1539@p34>
On Tue, 27 Sep 2005 04:37:01 -0400 (EDT), Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>Simply copy some files *over NFS* from box1 to box2.
Which NFS? I've not had problems here with v3 + TCP, and each box
here uses NFS, I'd notice. Though I'm not using ACLs or any fancies.
>Or tar them, I did both.
>The remote machine locks and freezes, no console output.
>Copied 206MB before the MB/s went to 0 and crashed the remote box.
I'm unpacking source tarballs and patching from NFS mounted file
mirror / server. I'd surely notice if NFS stopped working here.
>Nasty bug. SCP works fine.
>I've reported this before w/ .config etc but nobody responded.
NFS kernel options, exports, fstab mount options, and a test case
please?
Cheers,
Grant.
next prev parent reply other threads:[~2005-09-27 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 8:37 Justin Piszcz
2005-09-27 9:03 ` Grant Coady [this message]
2005-09-27 9:27 ` Grant Coady
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=u62ij19vjosurf6h3dovph0gcgmp3tdpth@4ax.com \
--to=grant_lkml@dodo.com.au \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
/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®