From: Rich Freeman <rich0@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Soliciting new RAID ideas
Date: Tue, 27 May 2014 20:26:41 -0400 [thread overview]
Message-ID: <CAGfcS_nKVbJ-gNTd6tZAGKwq=Gr1RE1vTmaydGA1E=auzStSRw@mail.gmail.com> (raw)
In-Reply-To: <dfd718f8f9a0570aa19880f354b5dbef@thegeezer.net>
On Tue, May 27, 2014 at 7:38 PM, <thegeezer@thegeezer.net> wrote:
> if you had lvm already you could
> simply 'move' then 'enlarge' your existing stuff (tm)
Yup - if you're not running btrfs/zfs you probably should be running
lvm. One thing I would do is backup your lvm metadata when it changes
- I once got burned by an lvm error of some kind and an fsck scrambled
the living daylights out of my disk (an fsck on one ext3 partition
scrambled a different partition). That is pretty rare though (but I
did find one or two mentions online of similar situations.
> : i'd like to know how
> btrfs would do the same for anyone who can let me know.
A btrfs filesystem pools storage. You can add devices to the pool,
and remove devices to the pool. If you remove a device with data on
it the data will get moved. When adding devices btrfs does not
automatically shuffle data around - you can issue a balance command to
do so, but I wouldn't do this until you're done adding/removing
drives.
A nice thing about btrfs is that devices do not have to be of the same
size and it generally does the right thing.
The downside of btrfs right now for raid is that raid5/6 are still
very experimental. They will support reshaping though, which is one
of the reasons I've stayed away from zfs. Zfs also lets you
add/remove devices from a pool, but it does not allow you to reshape a
raid.
Rich
next prev parent reply other threads:[~2014-05-28 0:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 22:13 [gentoo-amd64] Soliciting new RAID ideas Mark Knecht
2014-05-27 22:39 ` Bob Sanders
2014-05-27 22:58 ` Harry Holt
2014-05-27 23:38 ` thegeezer
2014-05-28 0:26 ` Rich Freeman [this message]
2014-05-28 3:12 ` [gentoo-amd64] btrfs Was: " Duncan
2014-05-28 7:29 ` thegeezer
2014-05-28 20:32 ` Marc Joliet
2014-05-29 6:41 ` [gentoo-amd64] " Duncan
2014-05-29 17:57 ` Marc Joliet
2014-05-29 17:59 ` Rich Freeman
2014-05-29 18:25 ` Mark Knecht
2014-05-29 21:05 ` Frank Peters
2014-05-30 2:04 ` [gentoo-amd64] amd64 list, still useful? Was: btrfs Duncan
2014-05-30 2:44 ` Frank Peters
2014-05-30 6:25 ` [gentoo-amd64] " Duncan
2014-06-04 16:41 ` [gentoo-amd64] " Mark Knecht
2014-06-05 2:00 ` [gentoo-amd64] " Duncan
2014-06-05 18:59 ` Mark Knecht
2014-06-06 12:11 ` Duncan
[not found] ` <Alo71o01J1aVA4001lo9xP>
2014-06-06 17:07 ` Duncan
2014-05-27 23:32 ` [gentoo-amd64] Soliciting new RAID ideas Mark Knecht
2014-05-27 23:51 ` Marc Joliet
2014-05-28 15:26 ` Bob Sanders
2014-05-28 15:28 ` Bob Sanders
2014-05-28 16:10 ` Rich Freeman
2014-05-28 19:20 ` Marc Joliet
2014-05-28 19:56 ` Bob Sanders
2014-05-29 7:08 ` [gentoo-amd64] " Duncan
2014-05-27 23:05 ` [gentoo-amd64] " Alex Alexander
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='CAGfcS_nKVbJ-gNTd6tZAGKwq=Gr1RE1vTmaydGA1E=auzStSRw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-amd64@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