From owner-freebsd-questions@FreeBSD.ORG Tue Feb 3 18:39:04 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56B6E106566C for ; Tue, 3 Feb 2009 18:39:04 +0000 (UTC) (envelope-from john@zog.net) Received: from atacama.88.net (atacama.88.net [212.13.194.140]) by mx1.freebsd.org (Postfix) with ESMTP id 161528FC14 for ; Tue, 3 Feb 2009 18:39:03 +0000 (UTC) (envelope-from john@zog.net) Received: from localhost (localhost [127.0.0.1]) by atacama.88.net (Postfix) with ESMTP id D47D62645BA for ; Tue, 3 Feb 2009 18:22:00 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at 88.net Received: from atacama.88.net ([127.0.0.1]) by localhost (atacama.88.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Th1UyN2hIr4g for ; Tue, 3 Feb 2009 18:21:59 +0000 (GMT) Received: from [192.168.2.199] (AMontsouris-551-1-53-182.w90-24.abo.wanadoo.fr [90.24.172.182]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by atacama.88.net (Postfix) with ESMTPSA id 01EC4264411 for ; Tue, 3 Feb 2009 18:21:58 +0000 (GMT) Message-Id: <158E6ABD-6BCF-4222-AD59-9B43FE6832D5@zog.net> From: John Morgan Salomon To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 3 Feb 2009 19:21:50 +0100 X-Mailer: Apple Mail (2.929.2) Subject: NFSv2 Wrong FS Size X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2009 18:39:04 -0000 Hi there, I'm facing an odd problem with an NFSv2 mount. I'm using userland nfsd from a Buffalo TeraStation Pro v1 NAS, running PPC Linux 2.4.20. root@LEVIATHAN:~# uname -a Linux LEVIATHAN 2.4.20_mvl31-ppc_terastation #3 Tue Jul 18 09:29:11 JST 2006 ppc GNU/Linux I am sharing the following filesystem: root@LEVIATHAN:~# df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/md1 1755708928 979032844 776676084 56% /mnt/array1 /etc/exports looks as follows: /mnt/array1/data 192.168.2.0/255.255.255.0(rw,sync,insecure) Mounting this on my Macbook Pro: Fluffy:~ root# mount_nfs 192.168.2.11:/mnt/array1/data /mnt Fluffy:~ root# df -k Filesystem 1024-blocks Used Available Capacity Mounted on 192.168.2.11:/mnt/array1/data 1755708928 979032844 776676084 56% /mnt So far, so good... Mounting this on a FreeBSD 7.1 client: behemoth# mount /data behemoth# df -k Filesystem 1024-blocks Used Avail Capacity Mounted on 192.168.2.11:/mnt/array1/data -391774720 -1168450804 776676084 298% /data Here is my fstab: 192.168.2.11:/mnt/array1/data /data nfs rw 0 0 Woo. 298%! That's a record, even for me. I've tried mount_nfs with -2, -T, and I can't think of anything else. There are no telling log messages, either on the NAS or on the FreeBSD box. behemoth# uname -a FreeBSD behemoth 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #2: Sat Jan 31 20:13:15 CET 2009 root@behemoth:/usr/obj/usr/src/sys/BEHEMOTH i386 Any ideas? It's causing various php scripts that need an accurate filesystem size to puke all over the place. Help! Thanks much for any thoughts, -John