From owner-freebsd-stable@FreeBSD.ORG Wed Jan 7 02:45:25 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F954106564A for ; Wed, 7 Jan 2009 02:45:25 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by mx1.freebsd.org (Postfix) with ESMTP id 56D038FC27 for ; Wed, 7 Jan 2009 02:45:25 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from localhost (localhost [127.0.0.1]) by ly.sdf.com (Postfix) with ESMTP id A3B11244727; Tue, 6 Jan 2009 18:18:43 -0800 (PST) X-Virus-Scanned: amavisd-new at ly.sdf.com Received: from ly.sdf.com ([127.0.0.1]) by localhost (ly.sdf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tdgLYwMN7enH; Tue, 6 Jan 2009 18:18:38 -0800 (PST) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by ly.sdf.com (Postfix) with ESMTP id C5A3B244762; Tue, 6 Jan 2009 18:18:38 -0800 (PST) Date: Tue, 6 Jan 2009 18:18:38 -0800 (PST) From: Tom Samplonius To: SDH Admin Message-ID: <17218792.31231294718710.JavaMail.root@ly.sdf.com> In-Reply-To: <006401c96477$3dd8e440$b98aacc0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [216.113.208.148] X-Mailer: Zimbra 5.0.11_GA_2695.RHEL4 (ZimbraWebClient - FF3.0 (Win)/5.0.11_GA_2695.RHEL4) Cc: freebsd-stable@freebsd.org Subject: Re: ver 4.2 won't allow save because it can't see 2.2T disk drive X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 02:45:25 -0000 ----- "SDH Admin" wrote: > >I need to patch this until I can update the system, any pointers to > >where (if there is one) to get the patch for this, and installation > >instructions. > > What is the 2.2T disk formatted as? Can you give more details on your > hardware (storage device and the 4.2 server), as well as posting your > dmesg > output. In this case, it is pretty clear the the 2.2TB disk is mounted on NFS. And the OP said it was a StorageVault, so that means it is a WAFL filesystem, which is meaningless here. Is it really FreeBSD 4.2? Anyways, it doesn't really matter what "df" reports. If df is folding some of the 64bit values in negative numbers, it is no issue really. But if the StorageVault is returning errors when files are created or written to, then that is probably a configuration issue. NFS is a client-server filesystem. So "df" on NFS just queries the StorageVault for the info, and displays it. The NFS client doesn't shutdown, because the filesystem appear to be full, or have negative capacity. Tom