From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Drive gone bad, now what?
Date: Tue Oct 28 02:20:02 2003 [thread overview]
Message-ID: <20031028081933.GA1629@tykepenguin.com> (raw)
In-Reply-To: <3F9DB7D8.5080502@xs4all.nl>
On Tue, Oct 28, 2003 at 01:27:04AM +0100, Gert van der Knokke wrote:
> John Stoffel wrote:
>
> >Gert> I didn't expect lvm to restore the missing data, I guessed it
> >Gert> would just let me access the rest of the data.
> >
> >At this point, you have to think, how can my filesystem cope with the
> >loss of a 60gb chunk of data in the middle (start or end even) of the
> >300+ gb of data? There's all sorts of meta-data and true data which
> >is now gone, and re-building the filesystem into a consistent state is
> >really impossible.
> >
> Hmm, and so I think LVM still needs a warning label :-)
>
> I wonder why LVM doesn't work the other way around:
> Create filesystems on several disks and then concatenate these to the
> outside as one large filesystem. This way if one drive goes bad you can
> always individually mount the drives and use the data.
>
> >If you are looking for a large/cheap/reliable bunch of storage,
> >instead of mirroring, you might want to think about RAID5 instead.
> >
> 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.
If a disk fails and you're not using RAID then you restore from backups.
--
patrick
next prev parent reply other threads:[~2003-10-28 2:20 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 [this message]
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
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=20031028081933.GA1629@tykepenguin.com \
--to=caulfield@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox