I have determined that a large array was created with an overly-large
chunk size. Best way to resize?
--
bill davidsen [EMAIL PROTECTED]
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
Ok tried the patch and got a kernel BUG this time (BUG_ON(k == conf-copies)?)
-John
Feb 15 12:52:35 testsvr kernel: md: recovery of RAID array md0
Feb 15 12:52:35 testsvr kernel: md: minimum _guaranteed_ speed: 1000
KB/sec/disk.
Feb 15 12:52:35 testsvr kernel: md: using maximum available idle
Oh, an additional piece of information I just realized I had not put
in my original email is that this failure only happens intermittenly
-- 50%-75% of the time a rebuild occurs
-John
On 2/15/07, John Stilson [EMAIL PROTECTED] wrote:
Ok tried the patch and got a kernel BUG this time (BUG_ON(k
help
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
unsubscribe linux-raid
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
(sorry for the direct spam, neil)
- Forwarded message from Dan Pritts [EMAIL PROTECTED] -
Date: Thu, 15 Feb 2007 13:42:36 -0500
From: Dan Pritts [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: minor cosmetic bug in md
Hi,
I wanted a linear device that included two partitions on the
On Thursday February 15, [EMAIL PROTECTED] wrote:
I have determined that a large array was created with an overly-large
chunk size. Best way to resize?
Dump and restore.
in-place reshapes (such as raid5 + 1 disk = raid6 or
change-chunk-size) are on my list of 'that might be interesting to
On Thursday February 15, [EMAIL PROTECTED] wrote:
Ok tried the patch and got a kernel BUG this time (BUG_ON(k == conf-copies)?)
Thanks obviously I missed some subtlety. I think I have it right
now.
I've tested this against a setup which I think is sufficiently
identical to yours this time
On Thursday February 15, [EMAIL PROTECTED] wrote:
Hi,
I wanted a linear device that included two partitions on the same disk
(I have my reasons).
I created it, it worked, yada yada.
But I got this error in my dmesg output:
md0: WARNING: hda5 appears to be on the same physical
I think I have found an easily-reproducible bug in Linux 2.6.20. I have
already applied the Fix various bugs with aligned reads in RAID5
patch, and that had no effect. It appears to be related to the resync
process, and makes the system lock up, hard.
The steps to reproduce are:
1. Be running
10 matches
Mail list logo
