From: Mark <musicman529@yahoo.com>
To: Christoph Litauer <litauer@uni-koblenz.de>,
Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: Performance problems with millions of inodes
Date: Wed, 25 Jun 2008 10:00:50 -0700 (PDT) [thread overview]
Message-ID: <889832.67139.qm@web34505.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080625180222.12885793@harpe.intellique.com>
What type of RAID? If striping is involved, perhaps you should investigate the "su" and "sw" suboptions.
I also found some performance improvement with "-l lazy-count=1", although you may not wish to slow down repair times for a backup volume.
--
Mark
"What better place to find oneself than
on the streets of one's home village?"
--Capt. Jean-Luc Picard, "Family"
next prev parent reply other threads:[~2008-06-25 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 14:43 Performance problems with millions of inodes Christoph Litauer
2008-06-25 14:46 ` Christoph Litauer
2008-06-25 16:02 ` Emmanuel Florac
2008-06-25 17:00 ` Mark [this message]
2008-06-26 11:29 ` Christoph Litauer
2008-06-25 23:12 ` Dave Chinner
2008-06-26 7:29 ` Christoph Litauer
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=889832.67139.qm@web34505.mail.mud.yahoo.com \
--to=musicman529@yahoo.com \
--cc=eflorac@intellique.com \
--cc=litauer@uni-koblenz.de \
--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