From: Stan Hoeppner <stan@hardwarefreak.com>
To: Igor M Podlesny <for.poige+lsr@gmail.com>
Cc: Peter Grandi <pg@lxra2.to.sabi.co.uk>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Software RAID checksum performance on 24 disks not even close to kernel reported
Date: Wed, 06 Jun 2012 23:59:40 -0500 [thread overview]
Message-ID: <4FD0353C.1050006@hardwarefreak.com> (raw)
In-Reply-To: <CA+sTkh6=Kn1EJ79zCxWW6Xr-H23E+-HpqJVD33vP4rJMQ3ON4g@mail.gmail.com>
On 6/6/2012 10:41 PM, Igor M Podlesny wrote:
> They try, for sure, but try is still a try. For e. g., you pvmove'd
> your LVM with XFS from one RAID to another one having different
> "layout", things can just stop working well all of the sudden.
Filesystems that have zero awareness of the storage geometry have poor
performance on striped RAID devices. XFS has excellent performance on
striped RAID specifically due to this awareness. Now you describe this
strength as a weakness due to a volume portability corner case no SA in
his right mind would attempt.
The proper way to do this is to perform an xfsdump of the filesystem to
a file, create a new XFS with the proper stripe geometry in the new
storage location (which takes all of 1 second BTW), then xfsrestore the
dump file.
And now you will say "Yes, but..."
--
Stan
next prev parent reply other threads:[~2012-06-07 4:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 23:14 Software RAID checksum performance on 24 disks not even close to kernel reported Ole Tange
2012-06-05 1:26 ` Joe Landman
2012-06-05 3:36 ` Igor M Podlesny
2012-06-05 7:47 ` Ole Tange
2012-06-05 11:25 ` Peter Grandi
2012-06-05 20:57 ` Ole Tange
2012-06-06 17:37 ` Peter Grandi
2012-06-05 14:15 ` Stan Hoeppner
2012-06-05 20:45 ` Ole Tange
2012-06-05 3:39 ` Igor M Podlesny
2012-06-05 7:47 ` Ole Tange
2012-06-05 11:29 ` Igor M Podlesny
2012-06-05 13:09 ` Peter Grandi
2012-06-05 21:17 ` Ole Tange
2012-06-06 1:38 ` Stan Hoeppner
2012-06-05 18:44 ` Ole Tange
2012-06-06 1:40 ` Brad Campbell
2012-06-06 3:48 ` Marcus Sorensen
2012-06-06 11:21 ` Ole Tange
2012-06-06 11:17 ` Ole Tange
2012-06-06 12:58 ` Brad Campbell
2012-06-06 14:11 ` Ole Tange
2012-06-06 16:05 ` Igor M Podlesny
2012-06-06 19:51 ` Ole Tange
2012-06-06 22:21 ` Igor M Podlesny
2012-06-06 22:53 ` Peter Grandi
2012-06-07 3:41 ` Igor M Podlesny
2012-06-07 4:59 ` Stan Hoeppner [this message]
2012-06-07 5:22 ` Igor M Podlesny
2012-06-07 9:03 ` Stan Hoeppner
2012-06-07 9:22 ` Igor M Podlesny
2012-06-06 16:09 ` Dan Williams
2012-06-06 19:19 ` Ole Tange
2012-06-06 19:24 ` Dan Williams
2012-06-06 19:26 ` Ole Tange
2012-06-07 4:06 ` Stan Hoeppner
2012-06-07 14:40 ` Joe Landman
2012-06-08 1:23 ` Stan Hoeppner
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=4FD0353C.1050006@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=for.poige+lsr@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=pg@lxra2.to.sabi.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.