On Thursday 2012-07-26 03:00, Phil Turmel wrote:
>> I used atop to show the transfer speeds to each drive. Here's a
>> screenshot:
>> http://img402.imageshack.us/img402/6484/screenshotfrom201207251.png
>
>[ The output of "lsdrv" [1] might be useful here, along with
>"mdadm -D /dev/md0" and "mdadm
On Thursday 2012-07-26 03:00, Phil Turmel wrote:
I used atop to show the transfer speeds to each drive. Here's a
screenshot:
http://img402.imageshack.us/img402/6484/screenshotfrom201207251.png
[ The output of lsdrv [1] might be useful here, along with
mdadm -D /dev/md0 and mdadm -E /dev/[b-j]
Kevin Ross wrote:
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
Kevin Ross wrote:
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
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 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 into that now.
Plus I disable the
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
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 shut down mythtv.
I will
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.
Or temporarily shut down mythtv.
I
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 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 into that now.
Plus I disable the on-drive
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 Wed, 2012-07-25 at 18:55 -0700, Kevin Ross wrote:
> 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
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; 3.2.24 does indeed have the fix.
--
To
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, the
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, the latest 3.2 stable does not contain
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.
Or
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 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, the latest 3.2 stable does not contain the
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, the
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; 3.2.24 does indeed have the fix.
--
To
On Wed, 2012-07-25 at 18:55 -0700, Kevin Ross wrote:
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 task
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
On Thu, Jul 26, 2012 at 5:55 AM, Kevin Ross wrote:
>
> 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
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
[Added linux-raid to the CC]
Hi Kevin,
Notes interleaved:
On 07/25/2012 06:52 PM, Kevin Ross wrote:
> 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.
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
[Added linux-raid to the CC]
Hi Kevin,
Notes interleaved:
On 07/25/2012 06:52 PM, Kevin Ross wrote:
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
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 Thu, Jul 26, 2012 at 5:55 AM, Kevin Ross ke...@familyross.net wrote:
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
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
38 matches
Mail list logo
