From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Kirch Subject: Re: [PATCH] statfs fails with EOVERFLOW Date: Tue, 23 Mar 2004 14:30:19 +0100 Sender: nfs-admin@lists.sourceforge.net Message-ID: <20040323133019.GD30984@suse.de> References: <20040323130513.GB30984@suse.de> <20040323132127.A322@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Cc: nfs@lists.sourceforge.net Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1B5lz4-0004Me-7n for nfs@lists.sourceforge.net; Tue, 23 Mar 2004 05:30:22 -0800 Received: from ns.suse.de ([195.135.220.2] helo=Cantor.suse.de) by sc8-sf-mx2.sourceforge.net with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.30) id 1B5lz3-0002yy-Jw for nfs@lists.sourceforge.net; Tue, 23 Mar 2004 05:30:21 -0800 To: Christoph Hellwig In-Reply-To: <20040323132127.A322@infradead.org> Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: On Tue, Mar 23, 2004 at 01:21:27PM +0000, Christoph Hellwig wrote: > On Tue, Mar 23, 2004 at 02:05:13PM +0100, Olaf Kirch wrote: > > I am currently dealing with a 2.6 bug report concerning statfs failing > > with EOVERFLOW. This happens on very large NFS file systems, and the > > problem is obviously that by default, we set s_blocksize to the wtmult > > value advertised by the server. If tbytes / wtmult exceeds 31 bits, statfs > > will fail with EOVERFLOW (on 2.4 it would silently produce crap values). > > that's why we have statfs64 in 2.6, a program with the right LFS magic > and a recentish glibc should use if for you. The glibc maintainers at suse tell me it's broken at the moment. Second, not all apps can easily be converted to LFS support. One of the apps that barfed was OpenOffice... be my guest and make it LFS clean :) And finally, I think it's really an NFS bug. A local statfs on the file system on the server works fine; it's just that the NFS client barfs because it uses wtmult as the block size (and if it's a v2 mount, things are even worse because it picks a totally arbitrary wtmult value of 512). Olaf -- Olaf Kirch | Stop wasting entropy - start using predictable okir@suse.de | tempfile names today! ---------------+ ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs