Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 21 Nov 2001 06:09:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 21 Nov 2001 06:09:11 -0500 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:36877 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Wed, 21 Nov 2001 06:09:00 -0500 Subject: Re: Swap To: helgehaf@idb.hist.no (Helge Hafting) Date: Wed, 21 Nov 2001 11:17:00 +0000 (GMT) Cc: nleroy@cs.wisc.edu (Nick LeRoy), linux-kernel@vger.kernel.org In-Reply-To: <3BFB7F2E.D45CB95C@idb.hist.no> from "Helge Hafting" at Nov 21, 2001 11:17:18 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > It is not a design bug - it is a design tradeoff. A stateful > server might work if you have years of uptime or at least > no unplanned downtime. But such implementations tend to force > clients to remount if the server ever go down. That may > be really annoying if you're accessing lots of servers. NFS is at best "imitation stateless". You can do good stateful servers that recover across both client and server machine failure. You can do far better with them than with NFS - its just a bit harder. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/