From: Norbert Veber <nveber@pyre.virge.net>
To: Dave Chinner <david@fromorbit.com>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: Small files perform much faster on newly formatted fs?
Date: Thu, 9 Jun 2011 20:54:57 -0400 [thread overview]
Message-ID: <20110610005457.GN28625@pyre.virge.net> (raw)
In-Reply-To: <20110609211731.GT32466@dastard>
On Fri, Jun 10, 2011 at 07:17:31AM +1000, Dave Chinner wrote:
> The mount options are only there to cahnge the alignment that
> already exists, and there are significant limitations on those
> changes.
Oh I see. I will reformat and set sunit/swidth for my current 3 disk
raid5 (2 data disks). What if I later add a 4th disk (3 data disks),
would using the mount option to specify the new swidth have any
performance hit?
I assume old files might work slower but any new data that is written
would be aligned across all the drives? Or should I just reformat again
at that point?
Thanks,
Norbert
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-06-10 0:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 16:37 Small files perform much faster on newly formatted fs? Norbert Veber
2011-06-08 7:11 ` Michael Monnerie
2011-06-08 12:26 ` Norbert Veber
2011-06-08 13:47 ` Michael Monnerie
2011-06-08 18:58 ` Norbert Veber
2011-06-09 5:44 ` Michael Monnerie
2011-06-08 20:52 ` Eric Sandeen
2011-06-08 21:16 ` Eric Sandeen
2011-06-09 1:29 ` Dave Chinner
2011-06-09 8:22 ` Christoph Hellwig
2011-06-09 13:48 ` Norbert Veber
2011-06-09 16:30 ` Michael Monnerie
2011-06-09 20:30 ` Norbert Veber
2011-06-09 21:17 ` Dave Chinner
2011-06-10 0:54 ` Norbert Veber [this message]
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=20110610005457.GN28625@pyre.virge.net \
--to=nveber@pyre.virge.net \
--cc=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--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