Date: Mon, 21 Apr 2003 14:15:37 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Jesse Geddis <freebsd@sgeine.net> Cc: freebsd-questions@freebsd.org Subject: Re: nfs filesystem size Message-ID: <20030421191537.GG28595@dan.emsphone.com> In-Reply-To: <PIEDIEIAPIPEKPNPJKAHAEIACHAA.freebsd@sgeine.net> References: <PIEDIEIAPIPEKPNPJKAHAEIACHAA.freebsd@sgeine.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Apr 21), Jesse Geddis said: > We have a NetApp FAS940 with a current storage size of 1.266 TB. FreeBSD is > reporting the following: > > Filesystem Size Used Avail Capacity Mounted on > /dev/da0s1a 2.0G 56M 1.8G 3% / > /dev/da0s1f 9.8G 1.9G 7.1G 21% /usr > /dev/da0s1g 5.2G 82M 4.7G 2% /usr/home > /dev/da0s1e 15G 161M 13G 1% /var > procfs 4.0K 4.0K 0B 100% /proc > 10.0.0.100:/vol/www01 -811.2G 465G 771G -57% /www > > is this a limitation of how large a filesystem freebsd can report or > are we running into something else that is fixable here? Thanks in > advance. I think I traced it to a variable overflow in nfs_vfsops.c:nfs_statfs(). I have a 1.4TB filesystem that occasionally (but not always) goes negative too. It just affects the results of the statfs/statvfs() calls, so the only thing it really hurts is 'df'. Filesystem Size Used Avail Capacity Mounted on novell1:/vol1 1.4T 1.1T 314G 78% /a/novell1/vol1 -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030421191537.GG28595>