From: Gert van der Knokke <gertk@xs4all.nl>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Drive gone bad, now what?
Date: Tue Oct 28 13:52:02 2003 [thread overview]
Message-ID: <3F9EC8AA.7080603@xs4all.nl> (raw)
In-Reply-To: <20031028081933.GA1629@tykepenguin.com>
Patrick Caulfield wrote:
>>>
>>>
>>No, what we're looking for is an 'expandable as needed' filesystem and
>>this is what LVM pretends to be.
>>
>>
>
>No. LVM does in no way "pretend to be a file system". It's an expandable block
>device. What the filesystem does with that block device is up to it.
>
>
Ok, this is a 'slight' mixup between what we need and what LVM provides.
>If a disk fails and you're not using RAID then you restore from backups.
>
>
>
Where on earth do you backup 300 Gb on ? On tapes ? For the price of a
tape device including tapes which can handle this amount of data you can
buy a lot of harddisks...
This is a very common problem nowadays with ultralarge drives becoming
available dirt cheap but reliability of these drives is to say 'not so good'
We are searching for a way to store large amounts of data reliable and
affordable on a system running as mass storage/archive for a small group
of users. Starting point will be around 300 to 400 Gb but in the near
future 1 Tb (and more...) The users must simply be able to 'store and
forget' on this system.
Traffic is fairly low but occasionally large amounts have to be
'restored or copied' to local (smaller) systems to be taken out on the road.
Raid5 is ok for fixed size systems, but a simple mirroring system would
be the most expandable with various size drives (in pairs ofcourse)
Maybe even two servers at different locations (then upgrading would mean
buying 4 drives at a time..)
Now we have to find a reliable resizable/expandable filesystem (or
resizable/expandable block device system) on this hardware.
Gert
next prev parent reply other threads:[~2003-10-28 13:52 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 [this message]
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
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=3F9EC8AA.7080603@xs4all.nl \
--to=gertk@xs4all.nl \
--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.