All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Briggs <jbriggs@esoft.com>
To: Miguel <turtle.power@wanadoo.es>
Cc: Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: "df -i" support
Date: Fri, 14 May 2004 11:50:09 -0600	[thread overview]
Message-ID: <1084557009.3263.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20040514194040.22389128.turtle.power@wanadoo.es>

On Fri, 2004-05-14 at 11:40, Miguel wrote:
> On Fri, 14 May 2004 12:55:53 -0400
> Valdis.Kletnieks@vt.edu wrote:
> 
> > On Fri, 14 May 2004 17:32:27 +0200, Miguel said:
> > 
> > > We are migrating our mtas from ext3 to reiserfs and the
> > > monitorization(a plugin) relies on the output of df -i, this output
> > > is very diferent between those filesystems, because reiserfs always
> > > return -1 as a total number of inodes.
> > 
> > The only reason you care about df -i is because on ext[23] and
> > similar, it is possible to run out of inodes before you run out of
> > files.  Since reiserfs allocates inodes as needed, you can't run out
> > of them unless you run out of space - in which case your monitoring
> > system should be flagging that.
> 
> No, we check this value to know how many files are in that
> partition (well an aproximation). I hope that this is true for ext2/3,
> isn't?
> 

Would this help you?

# cat /proc/fs/reiserfs/md1/oidmap

At the end of oidmap is a line like this:
total:  46 [46/972] used: 176147 [exact]

I think the used: 176147 is pretty close to what you want.  The number
goes up and down when I create or remove files.  When I ran 'find /
-xdev | wc -l' I got 174425.  I'm not sure where the extra 1,000+ comes
from.  

You would need to have CONFIG_REISERFS_PROC_INFO set in your kernel, and
of course you would need to replace md1 with whatever device you were
using.
-- 
Jonathan Briggs
jbriggs@esoft.com


  parent reply	other threads:[~2004-05-14 17:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13  7:34 "df -i" support Miguel
2004-05-13  9:19 ` Vladimir Saveliev
2004-05-14 15:32   ` Miguel
2004-05-14 16:55     ` Valdis.Kletnieks
2004-05-14 17:40       ` Miguel
2004-05-14 17:48         ` Vladimir Saveliev
2004-05-14 18:26           ` Miguel
2004-05-14 17:50         ` Jonathan Briggs [this message]
2004-05-14 17:56           ` Nikita Danilov
2004-05-14 18:26           ` Miguel
2004-05-14 18:33             ` Nikita Danilov
2004-05-15 16:28               ` Carlos Carvalho
2004-05-14 18:48             ` Andreas Dilger
2004-05-14 19:06               ` Valdis.Kletnieks
2004-05-14 19:30                 ` Jeff Mahoney
2004-05-19 19:41               ` Miguel
2004-05-20 10:35                 ` Nikita Danilov
2004-05-20 19:44                   ` Miguel
2004-05-23 13:54           ` Miguel
2004-05-13  9:54 ` Dr. Giovanni A. Orlando
2004-05-14 15:35   ` Miguel

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=1084557009.3263.7.camel@localhost.localdomain \
    --to=jbriggs@esoft.com \
    --cc=Reiserfs-List@Namesys.COM \
    --cc=turtle.power@wanadoo.es \
    /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.