From: Chris Penney <cpenney@gmail.com>
To: Vincent Roqueta <vincent.roqueta@ext.bull.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: [CIRCUMVENTED] NFS client got stale NFS handle after server reboot
Date: Thu, 22 Sep 2005 12:27:33 -0400 [thread overview]
Message-ID: <111aefd0509220927881ad18@mail.gmail.com> (raw)
In-Reply-To: <200509221720.52412.vincent.roqueta@ext.bull.net>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On 9/22/05, Vincent Roqueta <vincent.roqueta@ext.bull.net> wrote:
>
> There are several problems using x86_64 linux NFS (v4) machines as server,
> and
> it seems to have several problems on 64 bits architectures in general (at
> least with x86_64 and ppc64. Surely other architectures)
>
> For now there are this issue yet known (linux 2.6.13+CITI, Linux
> 2.6.14-rc*
> +CITI)
> -> Socket error -11 closing a big file (server : x86_64, clients: x86,
> ppc64)
> -> wrong lock behaviours (Client PPC64, servers: ppc64, x86)
> -> Input/output error closing a big file (server: ppc64, client x86_64)
> -> Oops (Client x86_64, server x86_64) - Linux 2.6.13+CITI
>
> However, this issues concern NFSv4. I am going to try to reproduce your
> problem with NFSv3 and NFSv4.
>
I've not heard anything negative about x86_64 systems as NFS servers, but
this note is somewhat concerning to me as I've got some new AMD Opteron
hardware coming to replace some Pentium 4 NFS servers. We only use NFS v3
(mainly tcp). Should I be concerned? Should I use i386 mode instead of
x86_64?
Chris
[-- Attachment #2: Type: text/html, Size: 1456 bytes --]
next prev parent reply other threads:[~2005-09-22 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 15:17 NFS client got stale NFS handle after server reboot Reuti
2005-09-21 16:49 ` Reuti
2005-09-22 9:24 ` Reuti
2005-09-22 14:52 ` [CIRCUMVENTED] " Reuti
2005-09-22 15:20 ` Vincent Roqueta
2005-09-22 16:08 ` Chris Penney
2005-09-22 16:27 ` Chris Penney [this message]
2005-09-26 8:32 ` Reuti
-- strict thread matches above, loose matches on Subject: below --
2005-09-26 8:31 Reuti
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=111aefd0509220927881ad18@mail.gmail.com \
--to=cpenney@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=vincent.roqueta@ext.bull.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.