From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: extremely slow write performance plaintext
Date: Wed, 19 Jan 2011 03:59:06 -0600 [thread overview]
Message-ID: <4D36B5EA.6040603@hardwarefreak.com> (raw)
In-Reply-To: <1779_1295360207_4D35A0CF_1779_747_1_4D35A0CF.9050503@davisvision.com>
Cory Coager put forth on 1/18/2011 8:16 AM:
> No, it has never worked properly. Also, I want to stress that I am only having
> performance issues with one logical volume, the others seem fine.
Then, logically, there is something different about this logical volume than the
others. All of them reside atop the same volume group, atop the same two
physical RAID6 arrays, correct? Since I'm not quite tired of playing dentist (yet):
1. Were all of the LVs created with the same parameters? If so, can you
demonstrate verification of this to us?
2. Are all of them formatted with XFS? Were all formatted with the same XFS
parameters? If so, can you demonstrate verification of this to us?
3. Are you encrypting, at some level, the one LV that is showing low performance?
Cory: "The two arrays were added to a volume group and multiple logical volumes
were created."
4. Was this volume group preexisting? Are there other storage devices in this
volume group, or _only_ the RAID6 arrays?
5. Have you attempted deleting and recreating the LV with the performance issue?
6. How many total logical volumes are in this volume group?
7. What Linux distribution are you using? What kernel version?
We are not magicians here Cory. We need as much data from you as possible or we
can't help you. I thought I made this clear earlier. You need to gather as
much relevant data from that box as you can and present it here if you're
serious about solving this issue.
I get the feeling you just don't really care. In which case, why did you even
ask for help in the first place? Troubleshooting this issue requires your
_full_ participation and effort.
In these situations, it is most often the OP who solves his/her own issue, after
providing enough information here that we can point the OP in the right
direction. The key here is "providing enough information".
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-19 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:22 extremely slow write performance plaintext Cory Coager
2011-01-13 22:35 ` Emmanuel Florac
2011-01-14 0:17 ` Cory Coager
2011-01-14 19:51 ` Stan Hoeppner
2011-01-14 20:48 ` Cory Coager
2011-01-14 22:02 ` Stan Hoeppner
2011-01-18 14:16 ` Cory Coager
2011-01-19 9:59 ` Stan Hoeppner [this message]
2011-01-25 14:22 ` Cory Coager
2011-01-25 6:21 ` Michael Monnerie
2011-01-25 9:48 ` Mathieu AVILA
2011-01-25 14:25 ` Cory Coager
2011-01-28 6:22 ` Michael Monnerie
2011-01-28 13:08 ` Cory Coager
2011-01-25 14:27 ` Cory Coager
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=4D36B5EA.6040603@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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