Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: "Nuno Magalhães" <nunomagalhaes@eu.ipp.pt>, linux-raid@vger.kernel.org
Subject: Re: RAID newbie, 1 vs 5, chunk sizes
Date: Sun, 15 Jun 2014 22:23:00 -0400	[thread overview]
Message-ID: <539E5504.1080809@turmel.org> (raw)
In-Reply-To: <CADqA9ua4xuJM3J6mQY7jXrt-5f6Rsv3aFaxyiqL1e80t70R6Rg@mail.gmail.com>

On 06/14/2014 05:01 PM, Nuno Magalhães wrote:
> Hi,
> 
> Sorry if this is the wrong list. Most of the stuff out there seems
> outdated, and i have some specific doubts.
> 
> I'm trying to decide how to best create a RAID array and what
> configuration to use. This is a desktop system, nothing
> mission-critical, but i'd like it to be reasonably tailored to the
> hardware and intended usage, and have questions about default values.
> 
> Hardware:
>     1x Toshiba DT01ACA100 - 32MB bus, 931.0 GiB (1 TB; 1000204886016 bytes)
>     2x Seagate ST1000DM0003 - 64MB bus, 931.0 GiB (1 TB; 1000204886016 bytes)
> and
>     1x Maxtor 6G160E0 - 8MB bus, 149.1 GiB (160 GB; 160041885696 bytes)

Before going any further, check the TLER/ERC support for these drives.
(The Seagate xxxxxDM003 is ringing warning bells for me.)  The output of
"smartctl -l scterc /dev/sdX" for each one will do.  If you get anything
other than "7.0 seconds" or similar, you'll need special boot-time
scripting.  If you get "not supported", I wouldn't even consider putting
the drive into any raid array.

Search this list's archives for details on "timeout mismatch", "scterc",
and the consequences of ignoring this.

If you do have good error recovery timeouts, continue with Stan's advice.

Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-06-16  2:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 21:01 RAID newbie, 1 vs 5, chunk sizes Nuno Magalhães
2014-06-14 21:56 ` Stan Hoeppner
2014-06-15 11:50   ` Nuno Magalhães
     [not found]     ` <pmrj5x4rq3qbl6unnu7guho9.1402849407134@email.android.com>
2014-06-15 17:40       ` Nuno Magalhães
2014-06-16  2:23 ` Phil Turmel [this message]
2014-06-16 12:36   ` Nuno Magalhães
2014-06-16 13:19     ` Mark Knecht
2014-06-16 14:28     ` Phil Turmel
2014-06-16 16:14       ` Nuno Magalhães
2014-06-16 20:13         ` Phil Turmel
2014-06-16 21:02           ` Mark Knecht
2014-06-17  0:41         ` Nuno Magalhães
2014-06-17  0:47           ` Brad Campbell
2014-06-17  9:09             ` Nuno Magalhães
2014-06-17 19:50               ` Stan Hoeppner
2014-06-18  2:55               ` Brad Campbell
2014-06-18  7:33     ` Wilson, Jonathan
2014-06-18 10:19     ` Dag Nygren
2014-06-18 11:58       ` Mathias Burén
2014-06-18 12:16         ` Brad Campbell
2014-06-18 17:34         ` Roman Mamedov
2014-06-19  6:45           ` Wilson, Jonathan
2014-06-29 13:22             ` Nuno Magalhães

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=539E5504.1080809@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=nunomagalhaes@eu.ipp.pt \
    /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