From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262122AbTIHJI2 (ORCPT ); Mon, 8 Sep 2003 05:08:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262123AbTIHJI2 (ORCPT ); Mon, 8 Sep 2003 05:08:28 -0400 Received: from angband.namesys.com ([212.16.7.85]:8900 "EHLO angband.namesys.com") by vger.kernel.org with ESMTP id S262122AbTIHJI1 (ORCPT ); Mon, 8 Sep 2003 05:08:27 -0400 Date: Mon, 8 Sep 2003 13:08:26 +0400 From: Oleg Drokin To: Rogier Wolff Cc: Hans Reiser , linux-kernel@vger.kernel.org, Nikita Danilov Subject: Re: First impressions of reiserfs4 Message-ID: <20030908090826.GB10487@namesys.com> References: <3F50D986.6080707@namesys.com> <20030831191419.A23940@bitwizard.nl> <20030908081206.GA17718@namesys.com> <20030908105639.B26722@bitwizard.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030908105639.B26722@bitwizard.nl> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello! On Mon, Sep 08, 2003 at 10:56:41AM +0200, Rogier Wolff wrote: > > > There is no installation program that will fail with: "Sorry, > > > you only have 100 million inodes free, this program will need > > > 132 million after installation", and it allows me a quick way > > > of counting the number of actual files on the disk.... > > You cannot. statfs(2) only exports "Total number of inodes on disk" and > > "number of free inodes on disk" values for fs. df substracts one from another one > > to get "number of inodes in use". > So, you report "oids_in_use + 100M" as total and "100M" as free inodes > on disk. Voila! Yes, we thought about that too. Need to be careful to not overflow "long int". And idea of filesystem with variable amount of inodes over time sounds confusing to me, too. > We're using a Unix operating system which has a bunch of standard > interfaces. The fun about using those is that lots of stuff "just works" > even if it wasn't designed to do exactly what you are doing right > now. So even if "df" wasn't designed to work on NFS, it still works. Yes. There is a special value of zero, that says "this field have absolutely no sence for this filesystem". Which is sort of our case. > But now we're going to get a new "df" which grabs the sysfs info and > uses that. But it won't work on reiserfs5, as the interface changes > again. Well, if current interface does not allow to see all the stuff you want to, time to change (introduce new one) interface, anyway. Bye, Oleg