From: Oleg Drokin <green@namesys.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org, Nikita Danilov <god@namesys.com>
Subject: Re: First impressions of reiserfs4
Date: Mon, 8 Sep 2003 13:08:26 +0400 [thread overview]
Message-ID: <20030908090826.GB10487@namesys.com> (raw)
In-Reply-To: <20030908105639.B26722@bitwizard.nl>
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
next prev parent reply other threads:[~2003-09-08 9:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 11:33 First impressions of reiserfs4 Erik Hensema
2003-08-30 17:06 ` Hans Reiser
2003-08-31 17:14 ` Rogier Wolff
2003-09-08 8:12 ` Oleg Drokin
2003-09-08 8:56 ` Rogier Wolff
2003-09-08 9:08 ` Oleg Drokin [this message]
2003-09-08 9:33 ` Rogier Wolff
2003-09-08 9:48 ` Oleg Drokin
2003-09-08 10:05 ` Rogier Wolff
2003-09-08 10:17 ` Oleg Drokin
2003-09-08 12:59 ` Herbert Poetzl
2003-09-08 22:24 ` Mike Fedyk
2003-09-09 7:04 ` Oleg Drokin
2003-09-09 19:10 ` Mike Fedyk
2003-09-11 10:29 ` Oleg Drokin
2003-09-11 17:15 ` Reiser3/4 & Ext2/3 was: " Mike Fedyk
2003-09-11 17:27 ` Oleg Drokin
2003-09-11 22:50 ` Rogier Wolff
2003-09-12 1:20 ` Bernd Eckenfels
2003-09-12 4:48 ` Mike Fedyk
2003-10-01 21:06 ` Bernd Eckenfels
2003-10-02 6:36 ` Hans Reiser
2003-09-12 1:17 ` Bernd Eckenfels
2003-09-08 20:11 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030908090826.GB10487@namesys.com \
--to=green@namesys.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=god@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.