From: Roberto Spadim <roberto@spadim.com.br>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: RAID HDDs spin up sequence
Date: Mon, 31 Jan 2011 19:35:29 -0200 [thread overview]
Message-ID: <AANLkTi=OBPdygcrCoEp1ypwYsdtyw0e-a7_pjPNG3ASL@mail.gmail.com> (raw)
In-Reply-To: <AANLkTingP1aKn2a3yrfN6W7zY-KcP8tLHvh+HxfLOGjs@mail.gmail.com>
i think yes (hd wake up on write/read command)
check linear and stripe layout
linear is like a lvm (concatenation)
i think raid0 work like stripe, but need to check it and return (raid0
= 0 = stripe level, linear!=raid0 for linux implementation)
2011/1/31 Mathias Burén <mathias.buren@gmail.com>:
> On 31 January 2011 21:25, Roberto Spadim <roberto@spadim.com.br> wrote:
>> just if you need information on all disks
>> define your read. are you reading 1 byte or many bytes (on all hds?)
>> the number of bytes read/write is the point
>> if you need another disk to read/write you need to wake up your another hd
>>
>> check this implementations on mdadm:
>> linear, raid0, 0, stripe
>> maybe one is better for low power than another, but maybe one is
>> faster than another
>>
>> 2011/1/31 Mathias Burén <mathias.buren@gmail.com>:
>>> On 31 January 2011 21:09, Roberto Spadim <roberto@spadim.com.br> wrote:
>>>> you psu must be dimensioned to work with everythink at full work load
>>>> (it´s a real production NAS right?! not a test)
>>>> your SAS/IDE/SATA controller and HDD manual should be checked
>>>> how hdd wake up? one command (read/write) over sata/sas/ide channel wake it up?
>>>> on linux raid we have a read algorithm and a write algorithm
>>>> if a raid1 write occur all disks will wake up
>>>> if a raid1 (raid0 or another) read occur only the disk will wake up
>>>>
>>>> but check you SATA/IDE/SATA controller, how it wake up your disk, and
>>>> how you hdd wake up
>>>>
>>>> 2011/1/31 Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>:
>>>>> Hi all,
>>>>>
>>>>> assuming there is a NAS, with, for example, 10 HDDs
>>>>> in RAID-6. Assuming the HDDs are put in standby, in
>>>>> order to save energy, when the NAS is not used.
>>>>> How is the spin up sequence when the corresponding
>>>>> /dev/mdX device is accessed?
>>>>> Will the system spin up one HDD at time or all together?
>>>>>
>>>>> Obviously, one at time will limit the peak current,
>>>>> thus allowing a better dimensioned PSU, working almost
>>>>> always around the optimal efficiency point.
>>>>>
>>>>> Thanks a lot for any information on the topic,
>>>>>
>>>>> bye,
>>>>>
>>>>> --
>>>>>
>>>>> piergiorgio
>>>>> --
>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Roberto Spadim
>>>> Spadim Technology / SPAEmpresarial
>>>> --
>>>> 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
>>>>
>>>
>>> I would guess, that on a RAID0 setup, any read to that md device would
>>> wake every disk up in that setup. No?
>>>
>>> // Mathias
>>>
>>>
>>
>>
>>
>> --
>> Roberto Spadim
>> Spadim Technology / SPAEmpresarial
>>
>
> I meant "default RAID0 setup with mdadm", with a minimum of 2 HDDs,
> and any fs on top of that. (with or without lvm)
>
> Unless the file is very small (smaller than the minimum piece of data
> that's being spread across all devices in the RAID0 setup (btw, that's
> this called in RAID0, is it chunk size? Stripe size?)) or cached,
> you'll wake the HDDs up. Right?
>
> // Mathias
> --
> 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
>
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
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
next prev parent reply other threads:[~2011-01-31 21:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 20:18 RAID HDDs spin up sequence Piergiorgio Sartor
2011-01-31 21:09 ` Roberto Spadim
2011-01-31 21:10 ` Roberto Spadim
2011-01-31 21:11 ` Mathias Burén
2011-01-31 21:25 ` Roberto Spadim
2011-01-31 21:29 ` Mathias Burén
2011-01-31 21:35 ` Roberto Spadim [this message]
2011-01-31 22:23 ` Piergiorgio Sartor
2011-01-31 22:42 ` Roberto Spadim
2011-01-31 22:42 ` Roberto Spadim
2011-01-31 23:07 ` Piergiorgio Sartor
2011-01-31 23:12 ` Roberto Spadim
2011-02-01 1:45 ` Phillip Susi
2011-02-01 12:39 ` Roman Mamedov
2011-02-01 13:10 ` John Robinson
2011-02-01 21:37 ` Stan Hoeppner
2011-02-01 22:46 ` Roberto Spadim
2011-02-01 13:55 ` brian.foster
2011-02-01 14:37 ` Roberto Spadim
2011-02-01 14:44 ` Roberto Spadim
2011-02-01 15:01 ` John Robinson
2011-02-01 15:46 ` Roberto Spadim
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='AANLkTi=OBPdygcrCoEp1ypwYsdtyw0e-a7_pjPNG3ASL@mail.gmail.com' \
--to=roberto@spadim.com.br \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=piergiorgio.sartor@nexgo.de \
/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).