From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: adfas asd <chimera_god@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: A few remaining questions about installing to RAID-10
Date: Sat, 3 Oct 2009 23:59:33 -0600 [thread overview]
Message-ID: <200910032359.33804.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <263762.74813.qm@web38801.mail.mud.yahoo.com>
On Sat October 3 2009, adfas asd wrote:
> --- On Sat, 10/3/09, Drew <drew.kay@gmail.com> wrote:
> > From: Drew <drew.kay@gmail.com>
> >
> > > I didn't use LVM, and don't
> >
> > trust layering of any technology.
> >
> > I'm curious as to why you say that?
> >
> > From my experience almost everything in software is layered
> > or an
> > abstraction. The Network & Storage stacks are just
> > layers of code
> > running over top other lower layers. LVM & RAID are
> > just another layer
> > in the storage stack, and well tested ones I might add.
>
> Feel free. But the more direct a system, the more reliable it is. Basic
> scientific principle.
>
> To me, LVM just adds a function (expansion) which should be in the RAID
> module (and likely soon will be), yet adds a whole 'nother layer of
> complexity. No thanks. BTRFS addresses all these issues, but I was an
> early adopter and got burned by the loss of my data at a crucial point.
>
It actually adds volumes, something you just don't get with mdraid. Unless you
count partitions, but that is just.. ew. I had LVM blow up in my face too, but
it wasn't LVM's fault, it was mine ;) I was the one that was running a "big"
(for me, at the time) jbod array with no backups. I can hardly blame the loss
of that data on LVM.
>
>
> --
> 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
>
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next prev parent reply other threads:[~2009-10-04 5:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 1:27 A few remaining questions about installing to RAID-10 Ben DJ
2009-10-02 2:31 ` Ben DJ
2009-10-02 3:16 ` Neil Brown
2009-10-02 3:46 ` Ben DJ
2009-10-02 12:30 ` adfas asd
2009-10-02 14:54 ` Ben DJ
2009-10-02 15:06 ` Keld Jørn Simonsen
2009-10-02 15:15 ` Robin Hill
2009-10-02 15:46 ` Ben DJ
2009-10-02 15:59 ` Robin Hill
2009-10-02 16:31 ` Ben DJ
2009-10-02 17:01 ` Robin Hill
2009-10-02 17:24 ` Ben DJ
2009-10-03 14:12 ` adfas asd
2009-10-03 16:55 ` Keld Jørn Simonsen
2009-10-03 17:02 ` Thomas Fjellstrom
2009-10-03 19:05 ` Drew
2009-10-03 21:09 ` adfas asd
2009-10-04 5:59 ` Thomas Fjellstrom [this message]
2009-10-05 4:59 ` Leslie Rhorer
2009-10-05 13:58 ` adfas asd
2009-10-02 7:51 ` Keld Jørn Simonsen
2009-10-02 7:54 ` Robin Hill
[not found] <20091005145711322.FNMG18886@cdptpa-omta02.mail.rr.com>
2009-10-05 15:30 ` adfas asd
2009-10-05 15:49 ` Drew
2009-10-05 15:55 ` adfas asd
2009-10-05 16:19 ` Drew
2009-10-05 18:13 ` Leslie Rhorer
2009-10-05 18:41 ` Drew
2009-10-06 0:50 ` Leslie Rhorer
2009-10-06 3:42 ` Drew
2009-10-06 9:11 ` Keld Jørn Simonsen
2009-10-06 13:24 ` adfas asd
2009-10-06 22:57 ` Ben DJ
2009-10-07 17:58 ` adfas asd
2009-10-25 5:20 ` Leslie Rhorer
2009-10-05 18:03 ` Leslie Rhorer
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=200910032359.33804.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--cc=chimera_god@yahoo.com \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).