From: Chris Cox <chris_cox@stercomm.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Drive gone bad, now what?
Date: Tue Oct 28 14:55:02 2003 [thread overview]
Message-ID: <3F9ED74D.3050709@stercomm.com> (raw)
In-Reply-To: <3F9EC8AA.7080603@xs4all.nl>
(orginally wasn't going to send this.. but changed my mind)
First, let me say that 100's of GB is nothing today.
A good LTO2 unit will do the trick quite nicely. The problem
is that we are talking about 100's of TB now. Even if
you have a 100 tape LTO2 drive or multiple LTO2 arrays
capable of moving 50M/sec+... you still end up in a crunch.
SAN folks will tell you to live mirror to a remote DR site...
but the pipe between sites could be VERY expensive (if you
have the money, it is definitely something worth considering
though). What I'm suggesting below.. and I've tried to
use LVM... is the use of mirrored drives and the idea of
archival of hard disk storage.
Gert van der Knokke wrote:
...
> Now we have to find a reliable resizable/expandable filesystem (or
> resizable/expandable block device system) on this hardware.
Mirrored drives. So a logical drive includes a mirror as well.
You'll need a raid controller that can configure many drive instances
(drive + mirror). Use LVM to add new logical drives into your
volume group, then extend your volumes and resize your filesystems.
(ascii art)
pv1 pv2
+-----+ +-----+
| d 1 | | d 2 |
+-----+ +-----+
| m 1 | | m 2 |
+-----+ +-----+
pvcreate on pv1 and pv2 (can add pv3, etc later as needed)
put pv1, pv2 into a vg (extend with additional pv's later)
(if you like the pv's could be a set of mirrored drives
which are also striped).
Mirrored set could be pulled and archived at a storage center or
moved to a disaster recovery site. Of course, this does imply
the ability to take out the entire range of mirrors safely.
You'll have to look at your HW raid controller to see what
is possible. Afterwards, replace the "m" drives and let them
rebuild.
You may ask about joining the drives at the HW RAID level.. but as
mentioned, this might not give you the flexibility desired (see
the idea of striped sets mentioned earlier).
There are probably better solutions to this... obviously some
high end SAN devices may be better suited... not sure about
Linux filesystem compatibility though).
Just an idea.
Today, we're using a 5 TB disk based cache feeding into a
72 tape LTO library with 2 drives... adequate for our needs,
but we just don't have the storage needs that some require.
Moving forward, the idea of using off site disk storage,
off site DR replication or live DR mirroring are things we'll
haved to look at.
next prev parent reply other threads:[~2003-10-28 14:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 15:10 [linux-lvm] RAID 1 on Device Mapper - best practices? John Stoffel
2003-10-17 15:29 ` Mike Williams
2003-10-17 15:51 ` John Stoffel
2003-10-17 15:56 ` [linux-lvm] " Måns Rullgård
2003-10-17 16:13 ` [linux-lvm] " Mike Williams
2003-10-22 8:02 ` wopp
2003-10-23 17:52 ` [linux-lvm] Drive gone bad, now what? Gert van der Knokke
2003-10-23 18:59 ` John Stoffel
2003-10-24 0:22 ` Rickard Olsson
2003-10-24 15:23 ` Gert van der Knokke
2003-10-27 8:59 ` John Stoffel
2003-10-27 18:28 ` Gert van der Knokke
2003-10-28 2:20 ` Patrick Caulfield
2003-10-28 13:52 ` Gert van der Knokke
2003-10-28 14:14 ` Jayson Garrell
2003-10-28 14:30 ` Gert van der Knokke
2003-10-28 15:36 ` John Stoffel
2003-10-29 8:54 ` Brian J. Murrell
2003-10-30 8:00 ` Petro
2003-11-26 10:15 ` Harri Haataja
2003-10-28 16:06 ` Glen Harris
2003-10-28 14:55 ` Chris Cox [this message]
2003-10-28 8:57 ` Mark H. Wood
2003-10-28 8:40 ` Mark H. Wood
2003-10-23 18:53 ` [linux-lvm] RAID 1 on Device Mapper - best practices? John Stoffel
2003-11-20 7:20 ` Gregory K. Ruiz-Ade
2003-11-20 8:33 ` [linux-lvm] " Måns Rullgård
2003-11-21 13:02 ` Micah Anderson
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 0:54 [linux-lvm] Drive gone bad, now what? Victor Tan
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=3F9ED74D.3050709@stercomm.com \
--to=chris_cox@stercomm.com \
--cc=linux-lvm@sistina.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.