From: "Daniele P." <daniele@interline.it>
To: xfs@oss.sgi.com
Subject: Re: Inode usage
Date: Thu, 19 Apr 2007 15:42:53 +0200 [thread overview]
Message-ID: <200704191542.53366.daniele@interline.it> (raw)
In-Reply-To: <20070419131442.GC32602149@melbourne.sgi.com>
On Thursday 19 April 2007 15:14, you wrote:
> On Thu, Apr 19, 2007 at 10:28:46AM +0200, Stein M. Hugubakken wrote:
> > Hi!
> >
> > I have a lot of free inodes on my xfs-partitions and was wondering
> > about what impact this has on performance or memory?
>
> None. The number of free inodes is a made up number. ;)
That's for normal usage.
Well, David don't forget what you tell me some time ago about
xfs_repair
In terms of inode count, I generally use the rule that for every
10million inodes you need a gigabyte of RAM for repair - you needed
about 500MB for 6million inodes.
The inode count also affects xfsdump/xfsrestore operations but I don't
know the details. There was a huge improvement in performances for
partial dump with xfsprogs-2.8.16 IIRC.
Regards,
Daniele P.
next prev parent reply other threads:[~2007-04-19 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 8:28 Inode usage Stein M. Hugubakken
2007-04-19 13:14 ` David Chinner
2007-04-19 13:42 ` Daniele P. [this message]
2007-04-19 13:50 ` Daniele P.
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=200704191542.53366.daniele@interline.it \
--to=daniele@interline.it \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox