From owner-freebsd-stable@FreeBSD.ORG Wed Jan 7 14:11:46 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 647241065673 for ; Wed, 7 Jan 2009 14:11:46 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id D399B8FC17 for ; Wed, 7 Jan 2009 14:11:45 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n07EBhPG045593; Wed, 7 Jan 2009 15:11:44 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n07EBg8l045592; Wed, 7 Jan 2009 15:11:42 +0100 (CET) (envelope-from olli) Date: Wed, 7 Jan 2009 15:11:42 +0100 (CET) Message-Id: <200901071411.n07EBg8l045592@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, tom@samplonius.org, admin@stardothosting.com In-Reply-To: <17218792.31231294718710.JavaMail.root@ly.sdf.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 07 Jan 2009 15:11:44 +0100 (CET) Cc: 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 Reply-To: freebsd-stable@FreeBSD.ORG, tom@samplonius.org, admin@stardothosting.com 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 14:11:46 -0000 Tom Samplonius wrote: > 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. It depends on the application of the OP. If it queries the free space on the device before writing data to it, then the negative numbers might indeed be a problem. If the application forks df(1), a very simple work-around would be to install a small wrapper script that prints some values that the application is happy with. However, if the application calls getfsstat(2), it will be more difficult to work around. By the way, the fields in the statfs structure were changed from 32bit signed values to 64bit unsigned values between FreeBSD 5.1 and 5.2. So, in order to solve the problem, the OP would have to update at least to FreeBSD 5.2. (Don't get me wrong; I do not recommend to install 5.2; it's five years old and not supported anymore. If you update, I'd recommend to go for the latest release, which is 7.1 right now.) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one?" -- Tom Cargil, C++ Journal