From: Spelic <spelic@shiftmail.org>
To: xfs@oss.sgi.com
Subject: Verify filesystem is aligned to stripes
Date: Wed, 24 Nov 2010 19:39:56 +0100 [thread overview]
Message-ID: <4CED5BFC.8000906@shiftmail.org> (raw)
Hi there,
I thought there was a way to empirically check that the filesystem is
correctly aligned to RAID stripes, but my attempts fail.
I don't mean by looking at sunit and swidth from xfs_info, because that
would not detect if there is some LVM offset problem.
I am particularly interested for parity RAIDs in MD.
I was thinking at "iostat -x 1": if writes are aligned I shouldn't see
any reads from the drives in a parity RAID...
unfortunately this does not work:
- a dd streaming write test has almost no reads even when I mount with
"noalign", with sufficiently large stripe_cache_size such as 1024. If it
is smaller, always reads, even if xfs is aligned.
- a kernel untar will show lots of reads at any stripe_cache_size even
if I'm pretty sure I aligned the stripes correctly on my 1024k x 15 data
disks and the .tar.bz2 file was in cache. I tried with both xfs stripes
autodetection in 2.6.37-rc2 and by specifying su and sw values by hand,
which turned out to be the same; I was without LVM so I'm pretty sure
alignment was correct. Why are there still lots of reads in this case?
so I'm pretty clueless. Anyone has good suggestions?
Thank you
PS, OT: do you confirm it's not a good idea to have agsize multiple of
stripe size like the mkfs warns you against? Today I offsetted it by +1
stripe unit (chunk) so that every AG begins on a different drive but
performances didn't improve noticeably. Wouldn't that cause more
unfilled stripes when writing?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-11-24 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 18:39 Spelic [this message]
2010-11-25 5:46 ` Verify filesystem is aligned to stripes Dave Chinner
2010-11-25 7:00 ` Stan Hoeppner
2010-11-25 10:15 ` Dave Chinner
2010-11-25 22:57 ` Stan Hoeppner
2010-11-26 8:16 ` Emmanuel Florac
2010-11-26 12:22 ` Dave Chinner
2010-11-26 13:15 ` Spelic
2010-11-26 14:05 ` Michael Monnerie
2010-11-26 14:36 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2010-11-26 2:43 Richard Scobie
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=4CED5BFC.8000906@shiftmail.org \
--to=spelic@shiftmail.org \
--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