On 07/27/2012 09:45 PM, Grant Coady wrote:
On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of "job one" on older kernels.
I have not, thanks for the tip, I'll look
On 07/27/2012 09:45 PM, Grant Coady wrote:
On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of job one on older kernels.
I have not, thanks for the tip, I'll look
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of "job one" on older kernels.
I have not, thanks for the tip, I'll look into that now.
Thanks!
-- Kevin
--
To unsubscribe from this list: send the line
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of job one on older kernels.
I have not, thanks for the tip, I'll look into that now.
Thanks!
-- Kevin
--
To unsubscribe from this list: send the line unsubscribe
On 07/26/2012 07:53 PM, Kevin Ross wrote:
On 07/26/2012 07:27 PM, David Dillow wrote:
On Thu, 2012-07-26 at 19:17 -0700, Kevin Ross wrote:
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel
On 07/26/2012 07:27 PM, David Dillow wrote:
On Thu, 2012-07-26 at 19:17 -0700, Kevin Ross wrote:
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel (3.4.6 right now).
As far as I can see
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel (3.4.6 right now).
As far as I can see, the latest 3.2 stable does not contain the delayed
stripe fix.
And I was looking at the wrong version;
On 07/25/2012 10:00 PM, Kevin Ross wrote:
unused devices:
# cat /proc/sys/dev/raid/speed_limit_min
1
MD is unable to reach its minimum rebuild rate while other system
activity is ongoing. You might want to lower this number to see if
that
gets you out of the stalls.
Or temporarily
On 07/25/2012 10:00 PM, Kevin Ross wrote:
unused devices:none
# cat /proc/sys/dev/raid/speed_limit_min
1
MD is unable to reach its minimum rebuild rate while other system
activity is ongoing. You might want to lower this number to see if
that
gets you out of the stalls
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel (3.4.6 right now).
As far as I can see, the latest 3.2 stable does not contain the delayed
stripe fix.
And I was looking at the wrong version;
On 07/26/2012 07:27 PM, David Dillow wrote:
On Thu, 2012-07-26 at 19:17 -0700, Kevin Ross wrote:
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel (3.4.6 right now).
As far as I can see
On 07/26/2012 07:53 PM, Kevin Ross wrote:
On 07/26/2012 07:27 PM, David Dillow wrote:
On Thu, 2012-07-26 at 19:17 -0700, Kevin Ross wrote:
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel
unused devices:
# cat /proc/sys/dev/raid/speed_limit_min
1
MD is unable to reach its minimum rebuild rate while other system
activity is ongoing. You might want to lower this number to see if that
gets you out of the stalls.
Or temporarily shut down mythtv.
I will try lowering those
On 07/25/2012 07:09 PM, CoolCold wrote:
You might be interested in write intent bitmap then, it gonna help a
lot. (resending in plain text)
Thanks, I'll look into that!
-- Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Thank you very much for taking the time to look into this.
On 07/25/2012 06:00 PM, Phil Turmel wrote:
Piles of small reads scattered across multiple drives, and a
concentration of queued writes to /dev/sda. What's on /dev/sda?
It's not a member of the raid, so it must be some other system
Hello,
I'm having a problem. After a while, my software RAID rebuild becomes
extremely slow, and the filesystem on the RAID is essentially blocked.
I don't know what is causing this. I guess it could be a bad drive, but
how can I find out?
I used atop to show the transfer speeds to each
Hello,
I'm having a problem. After a while, my software RAID rebuild becomes
extremely slow, and the filesystem on the RAID is essentially blocked.
I don't know what is causing this. I guess it could be a bad drive, but
how can I find out?
I used atop to show the transfer speeds to each
Thank you very much for taking the time to look into this.
On 07/25/2012 06:00 PM, Phil Turmel wrote:
Piles of small reads scattered across multiple drives, and a
concentration of queued writes to /dev/sda. What's on /dev/sda?
It's not a member of the raid, so it must be some other system
On 07/25/2012 07:09 PM, CoolCold wrote:
You might be interested in write intent bitmap then, it gonna help a
lot. (resending in plain text)
Thanks, I'll look into that!
-- Kevin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
unused devices:none
# cat /proc/sys/dev/raid/speed_limit_min
1
MD is unable to reach its minimum rebuild rate while other system
activity is ongoing. You might want to lower this number to see if that
gets you out of the stalls.
Or temporarily shut down mythtv.
I will try lowering
20 matches
Mail list logo
