From: Bill Davidsen <davidsen@tmr.com>
To: Linux Raid List <linux-raid@vger.kernel.org>
Subject: Speeding inode access
Date: Sun, 11 Sep 2011 13:41:49 -0400 [thread overview]
Message-ID: <4E6CF2DD.6000307@tmr.com> (raw)
I have an unusual application which modifies multi-MB parts of large
files and requires atime enabled for audit info. I am currently using
ext4 with the journal on SSD. The data io spread over the array members
nicely, but the inode io doesn't. Any thoughts on getting the inodes
inode io faster?
My thought is to create a raid0 with a small chunk size over multiple
drives, the existing raid6 with a large chunk size, and then concatenate
them so the inodes are at the start in the fast portion. I can increase
the number of inodes to take up the whole "fast" part and keep data in
the large chunk portion. I am not crazy about using some brand-new type
-f file system, but I'll listen to suggestions.
--
Bill Davidsen<davidsen@tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
reply other threads:[~2011-09-11 17:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E6CF2DD.6000307@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).