Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 6 Nov 2001 05:37:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 6 Nov 2001 05:37:05 -0500 Received: from trout.hpc.CSIRO.AU ([138.194.72.10]:37279 "EHLO trout.hpc.CSIRO.AU") by vger.kernel.org with ESMTP id ; Tue, 6 Nov 2001 05:36:57 -0500 Message-Id: <200111061036.VAA07886@trout.hpc.CSIRO.AU> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: linux-kernel@vger.kernel.org Subject: Re: Red Hat needs this patch (was Re: handling NFSERR_JUKEBOX) In-Reply-To: Your message of "06 Nov 2001 10:05:19 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Nov 2001 21:36:54 +1100 From: Bob Smart Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > If all you do is intercept read and setattr, then you certainly > haven't achieved 'enterprise quality'. I don't have documentation on when Cray's NFSv3 server will return NFSERR_JUKEBOX, but since inodes aren't migrated to tape I don't think it is likely on other than read and non-truncate write with no prior read. Our applications are unlikely to do the latter. Maybe there is a subset of servers for which the patch is OK, and we could make that clear in the help for the config option. I'll ask Cray for clarification about their server. Bob - 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/