From: Wols Lists <antlists@youngman.org.uk>
To: o1bigtenor <o1bigtenor@gmail.com>,
Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Raid settings
Date: Mon, 29 Aug 2016 12:16:47 +0100 [thread overview]
Message-ID: <57C4199F.5030601@youngman.org.uk> (raw)
In-Reply-To: <CAPpdf59b4Cd4CTa5Mfg=1qQk_Gvk4pr+Tm5YJ_5OD5STufzX2g@mail.gmail.com>
On 29/08/16 10:26, o1bigtenor wrote:
> I've looked but haven't been able to find anything that discusses the
> points that
> have been raised so far. Would you point me to a, or some, documents that
> discuss these options?
> What are the options besides the 2 you mentioned?
>
> What I'm looking for is a methodology for the decision rather than a blanket
> answer at this point. Thought initially that there might be a 'best' answer but
> now its looking like a much much more fluid thing.
Apropos all this, I should be getting write access to the linux raid
wiki sometime soon. At the moment, as I mentioned before, it seems to be
a cobweb site, with the admin MIA and stuck in the days of kernel 2.6,
LILO, and parallel ATA drives ... :-)
So I'm planning on a major update/rewrite, and I'll probably be bugging
the list for info :-) but this is exactly the sort of thing that might
well go on there, if I can find the info or get someone to write it for me.
Cheers,
Wol
next prev parent reply other threads:[~2016-08-29 11:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 21:43 Raid settings o1bigtenor
2016-08-28 21:59 ` Wols Lists
2016-08-29 2:28 ` o1bigtenor
2016-08-29 2:46 ` Adam Goryachev
2016-08-29 9:26 ` o1bigtenor
2016-08-29 11:16 ` Wols Lists [this message]
2016-08-29 12:11 ` o1bigtenor
2016-08-29 12:19 ` Wols Lists
2016-08-29 18:13 ` o1bigtenor
2016-08-29 18:43 ` Wols Lists
2016-08-29 6:18 ` Brad Campbell
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=57C4199F.5030601@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=o1bigtenor@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.