From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: Roberto Spadim <rspadim@gmail.com>
Cc: Jeff Johnson <jeff.johnson@aeoncomputing.com>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Best practice for large storage?
Date: Fri, 15 Feb 2013 00:23:13 +0100 (CET) [thread overview]
Message-ID: <29597293.40.1360884193537.JavaMail.root@zimbra> (raw)
In-Reply-To: <CAH3kUhGVt1iyn9tt=2-+f6H++obOGSK3x0pBBPZV8CFUXjp5yw@mail.gmail.com>
xfs+lvm+mdadm works, but I'm still back to my original question. I don't care about what filesystem is on top, only about the storage underneath. Read the original question again, please
----- Opprinnelig melding -----
xfs+lvm+mdadm don`t work? too complex?
2013/2/14 Roy Sigurd Karlsbakk < roy@karlsbakk.net >
----- Opprinnelig melding -----
> why not brtfs or xfs?
Well, because btrfs isn't stable and doesn't support RAID-[56] unless you're using the git tree for testing that, which is rather more unstable than the rest, and xfs is just a filesystem that needs to sit on top of a raid of some kind.
Vennlige hilsener / Best regards
roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
Roberto Spadim
--
Vennlige hilsener / Best regards
roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
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 parent reply other threads:[~2013-02-14 23:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH3kUhGVt1iyn9tt=2-+f6H++obOGSK3x0pBBPZV8CFUXjp5yw@mail.gmail.com>
2013-02-14 23:23 ` Roy Sigurd Karlsbakk [this message]
2013-02-14 23:42 ` Best practice for large storage? Roberto Spadim
2013-02-15 1:01 ` Adam Goryachev
2013-02-15 1:13 ` Roberto Spadim
2013-02-15 1:49 ` Growing a raid60 (Was: Re: Best practice for large storage?) Daniel Browning
[not found] <CAH3kUhFbR3coJSwPvqqOGrqcsvoJpdAPgAAiAgc_th1ym33DzA@mail.gmail.com>
2013-02-14 18:27 ` Best practice for large storage? Roy Sigurd Karlsbakk
2013-02-14 17:28 Roy Sigurd Karlsbakk
2013-02-14 17:33 ` Jeff Johnson
2013-02-14 17:39 ` Roy Sigurd Karlsbakk
2013-02-14 17:48 ` Jeff Johnson
2013-02-15 9:51 ` Sebastian Riemer
2013-02-16 12:48 ` Roy Sigurd Karlsbakk
2013-02-18 10:35 ` Sebastian Riemer
2013-02-16 5:40 ` Stan Hoeppner
2013-02-15 2:18 ` Chris Murphy
2013-02-16 7:09 ` Stan Hoeppner
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=29597293.40.1360884193537.JavaMail.root@zimbra \
--to=roy@karlsbakk.net \
--cc=jeff.johnson@aeoncomputing.com \
--cc=linux-raid@vger.kernel.org \
--cc=rspadim@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.