From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Intel(R) C600 SAS Controller
Date: Thu, 12 Jun 2014 10:15:08 +0200 [thread overview]
Message-ID: <5399618C.60606@xunil.at> (raw)
In-Reply-To: <5398B966.9020704@thegeezer.net>
Am 11.06.2014 22:17, schrieb thegeezer:
> On 06/11/2014 07:57 PM, Stefan G. Weichinger wrote:
>> looks promising:
>>
>
> awesome. i did have a look through the diff, there are lots of scsi
> drivers selected, storage (block) cgroups but i think the crucial factor
> was the HZ was set at 100 previously and 1000 now. i guess it has
> helped kernel-io though maybe a kernel hacker in here might give a more
> authoritative answer
The help suggests to choose 100 for servers ... the 1000 comes from the
sysresccd-setup, yes.
I wonder if chosing the "Processor Family" also had an influence.
And I even wonder more if I have some bad choices in my desktop's kernel
as well ;-) it's a grown setup over years ...
For now it looks good ... I will configure the current kernel as a
fallback kernel and maybe play with some options.
>> One big fat hw-RAID10 might be better?
>> But losing the wrong 2 drives makes it crash again ... afaik.
> yeah you could argue with raid6 you can _only_ lose two disks, whereas
> if you lose the right disks with raid01 you can lose 3 and still rebuild.
> raid 0+1 (as opposed to raid10, slightly different) gives you great
> speed and at least one drive you can lose.
> however, you are not protected by silent bit corruption but then you are
> using btrfs elsewhere.
... for the OS, yes ... and maybe for the target of virt-backup.
> myself i would use lvm to partition and then at least you can move
> things around later; btrfs lets you do the same afaiu
> _always_ have your hotspare in the system, then it takes less time to
> come back up to 100%
> nothing is quite as scary as having a system waiting on the post and a
> screwdriver before rebuild can even start
good suggestion, sure.
That would mean rebuilding the arrays to a RAID6 over 4 or 5 disks and
keeping one aside.
>> time for a break here.
> i'd strongly recommend such monitoring software as munin to have running
> -- this way you can watch trends like io times increasing over time and
> act on them before things start feeling sluggish
I will take a look into it and check how much time I need to learn and
set up.
> well earned break :)
;-)
S
prev parent reply other threads:[~2014-06-12 8:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 7:52 [gentoo-user] Intel(R) C600 SAS Controller Stefan G. Weichinger
2014-05-24 19:24 ` Stefan G. Weichinger
2014-05-26 17:47 ` Stefan G. Weichinger
2014-05-26 19:57 ` Stefan G. Weichinger
2014-05-27 13:03 ` Stefan G. Weichinger
2014-06-10 19:57 ` Stefan G. Weichinger
2014-06-10 20:02 ` Stefan G. Weichinger
2014-06-10 22:27 ` Stefan G. Weichinger
2014-06-11 8:47 ` Stefan G. Weichinger
2014-06-11 9:19 ` thegeezer
2014-06-11 9:34 ` Stefan G. Weichinger
2014-06-11 10:14 ` thegeezer
2014-06-11 10:27 ` thegeezer
2014-06-11 10:34 ` Stefan G. Weichinger
2014-06-11 10:41 ` thegeezer
2014-06-11 10:49 ` Stefan G. Weichinger
2014-06-11 11:01 ` thegeezer
2014-06-11 11:20 ` Stefan G. Weichinger
2014-06-11 11:18 ` thegeezer
2014-06-11 11:21 ` Stefan G. Weichinger
2014-06-11 11:52 ` thegeezer
2014-06-11 12:41 ` Stefan G. Weichinger
2014-06-11 13:32 ` thegeezer
2014-06-11 13:44 ` Stefan G. Weichinger
2014-06-11 14:15 ` Stefan G. Weichinger
2014-06-11 14:18 ` thegeezer
2014-06-11 14:38 ` Stefan G. Weichinger
2014-06-11 18:57 ` Stefan G. Weichinger
2014-06-11 20:17 ` thegeezer
2014-06-12 8:15 ` Stefan G. Weichinger [this message]
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=5399618C.60606@xunil.at \
--to=lists@xunil.at \
--cc=gentoo-user@lists.gentoo.org \
/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