I know this has come up before, but a few quick googles hasn't answered my
questions - I'm after the max. array size that can be created under
bog-standard 32-bit intel Linux, and any issues re. partitioning.
I'm aiming to create a raid-6 over 12 x 500GB drives - am I going to
have any problems?
Neil Brown wrote:
Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
My first guess is that it isn't listing /dev/sdd? somehow.
Otherwise, can you add a '-v' to the mdadm command that assembles the
array, and capture the output. That might be helpful.
NeilBrown
stupid me! I
On Wed, 2006-05-24 at 09:21 +0100, Gordon Henderson wrote:
I know this has come up before, but a few quick googles hasn't answered my
questions - I'm after the max. array size that can be created under
bog-standard 32-bit intel Linux, and any issues re. partitioning.
I'm aiming to create a
Mark Hahn wrote:
I just dd'ed a 700MB iso to /dev/null, dd returned 33MB/s.
Isn't that a little slow?
what bs parameter did you give to dd? it should be at least 3*chunk
(probably 3*64k if you used defaults.)
I would expect readahead to make this unproductive. Mind you, I didn't
say
On Wednesday May 24, [EMAIL PROTECTED] wrote:
I know this has come up before, but a few quick googles hasn't answered my
questions - I'm after the max. array size that can be created under
bog-standard 32-bit intel Linux, and any issues re. partitioning.
I'm aiming to create a raid-6 over
On Wednesday May 24, [EMAIL PROTECTED] wrote:
Mark Hahn wrote:
I just dd'ed a 700MB iso to /dev/null, dd returned 33MB/s.
Isn't that a little slow?
what bs parameter did you give to dd? it should be at least 3*chunk
(probably 3*64k if you used defaults.)
I would expect
On Wednesday May 24, [EMAIL PROTECTED] wrote:
Hi,
I upgraded my kernel from 2.6.15.6 to 2.6.16.16 and now the 'iostat -x
1' permanently shows 100% utilisation on each disk that member of an md
array. I asked my friend who using 3 boxes with 2.6.16.2 2.6.16.9
2.6.16.11 and raid1, he's
