linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: AndyLiebman@aol.com
To: neilb@cse.unsw.edu.au
Cc: linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE: mdadm 1.8.0 - A tool for managing Soft RAID under Linux
Date: Wed, 3 Nov 2004 07:15:01 EST	[thread overview]
Message-ID: <d9.18ba3ed3.2eba25c5@aol.com> (raw)

> neilb@cse.unsw.edu.au writes:
>
> Hmmm... I might work with 1.6 if you --build that raid0 (rather than
> --create),  or if you are using a 64bit processor like alpha or ia64. 
> But mdadm 1.6 definitely have problems in i386 processors when you try
> to --create a raid0 with devices larger than 2 terabytes.

I have been using "mdadm -Cv /dev/md0 -n2 -l0 -c[256 or 512] /dev/sd{a,b}" 
without incident. But I'll switch over to 1.8. 

Was the previous problem only one of creating the arrays? Or could there be 
further problems down the line with my arrays that were created with 1.6? 

By the way, do you know anybody with enough understanding of the Linux kernel 
to be able to rationally and logically tune the following items, which all 
relate to one another and MUST have some optimum settings for low-latency/high 
throughput over a network. 

* chunk size/stripe size of Hardware and Software arrays
* blockdev --setra (for each Hardware array)
* blockdev --setra (for each Linux Software array on top of Hardware)
* tcp items in /proc/sys/net/core and /proc/sys/net/ipv4 like rmem_max, 
wmem_max and the like

Regards, 
Andy Liebman

             reply	other threads:[~2004-11-03 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 12:15 AndyLiebman [this message]
2004-11-05  2:50 ` ANNOUNCE: mdadm 1.8.0 - A tool for managing Soft RAID under Linux Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-11-03  1:27 AndyLiebman
2004-11-03  3:38 ` Neil Brown
2004-11-02  3:38 Neil Brown
2004-11-28 20:01 ` Stephan van Hienen
2004-11-30  1:12   ` Neil Brown
2004-11-30  1:16     ` Stephan van Hienen

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=d9.18ba3ed3.2eba25c5@aol.com \
    --to=andyliebman@aol.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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;
as well as URLs for NNTP newsgroup(s).