From: Tim <tim@connectlive.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] offtopic but ...
Date: Wed May 8 08:23:02 2002 [thread overview]
Message-ID: <20020508082357.B18631@connectlive.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205081502560.3518-100000@diablo.unixag-zw.fh-kl.de>; from jovi@unixag-zw.fh-kl.de on Wed, May 08, 2002 at 03:12:45PM +0200
> Hehe Tim,
>
> that was fast, but as i told little bit lower in the email I dont want to
> put everything in a RAID. The RAID controller isnt the problem if you buy
> me a further 160GB Maxtor i will buy the RAID contoller or do
> software-RAID. ;-)
Fair enough. Personally (having to do this at work) I feel like an IDE
enclosure or a hardware RAID card is a relatively small investment in
data security, but then again, the 500GB I have live right now is not
content that I can tolerate data loss on. We probably should not use
IDE drives for it at all, except that it is replicated onto a whole
steaming mess of SCSI drives, also RAIDed up...
I think your requirements are different than the ones I am used to.
> The goal is simply to combine more diskspace+more security then just a
> LVM+one logical unit (mountpoint/device where you dont have to care all
> the time
> how the data gets stored and where)+better usage of the diskspace (you
> dont have on the one everything free and the other is halffull.
Makes sense, but I'm not sure how one would dynamically reallocate
parity information while everything is in-flight (eg. live).
> Or just imagine you would like to have 500gb and have only 4x3,5 slots to
> build the harddrives in and the maximum size is at the moment 160GB. How
> would you do it and you would give up some security for the advantage to
> have more space but not to lose everything if one drive fails.
> And the idea i described in the email below is somehow between a RAID0/LVM
> and a RAID5.
Again, the difference between my requirements and the ones you're
outlining is that I simply call a vendor and order another enclosure
when I need another 500GB.
I think I am beginning to see what your idea is, but the logistics of
having LVM take care of the metadata seem rather daunting.
--
We should take care not to make the intellect our god;
it has powerful muscles, but no personality.
--Albert Einstein
next prev parent reply other threads:[~2002-05-08 8:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 0:03 [linux-lvm] VG wiederfinden Tim-Christian.Hanschen
2002-05-08 6:46 ` Heinz J . Mauelshagen
2002-05-08 7:44 ` [linux-lvm] offtopic but Oliver Jovic
2002-05-08 7:48 ` Tim
2002-05-08 8:11 ` Oliver Jovic
2002-05-08 8:23 ` Tim [this message]
2002-05-08 9:11 ` Oliver Jovic
2002-05-08 11:20 ` Ragnar Kjørstad
2002-05-10 8:46 ` Heinz J . Mauelshagen
2002-05-08 9:11 ` Christian Limpach
2002-05-08 9:27 ` Steven Lembark
2002-05-13 4:37 ` Harri Haataja
2002-05-13 4:42 ` Patrick Caulfield
2002-05-13 7:37 ` Tim
2002-05-13 9:39 ` Steven Lembark
2002-05-13 10:21 ` Benjamin Scott
2002-05-13 15:32 ` Goetz Bock
2002-05-13 18:54 ` Benjamin Scott
2002-05-14 7:17 ` Goetz Bock
2002-05-14 7:46 ` Steven Lembark
2002-05-14 8:08 ` Benjamin Scott
2002-05-14 8:13 ` Tim
2002-05-13 9:29 ` Steven Lembark
2002-05-13 10:19 ` Benjamin Scott
2002-05-13 10:30 ` Steven Lembark
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=20020508082357.B18631@connectlive.com \
--to=tim@connectlive.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