Linux LVM users
 help / color / mirror / Atom feed
From: jens@pinguin.conetix.de
To: sleas@ixion.honeywell.com, linux-lvm@msede.com
Subject: [linux-lvm] LVM or mdutils/raidtools?
Date: Thu, 18 Feb 1999 20:03:12 +0100	[thread overview]
Message-ID: <19990218200312.C1529@debian.zuhause.de> (raw)
In-Reply-To: <Pine.GHP.4.05.9902161554060.25565-100000@ixion.honeywell.com>; from Shawn Leas on Tue, Feb 16, 1999 at 03:56:48PM -0600

On Tue, Feb 16, 1999 at 03:56:48PM -0600, Shawn Leas wrote:
> On Tue, 16 Feb 1999 jens@pinguin.conetix.de wrote:
> > not yet. I am wonderin whether I should. Or probably use
> > mdutils/raidtools instead. Maybe you can give me an ( unbiased ;> )
> > suggestion.
> Using LVM you would gain experience useful in Solaris, HPUX, etc...

I do not need that just yet, it's only a home system.

> Also, it's a LOT more flexible, and extensible.

ACK, but partitions do not change _that_ often round here. What I would
like, though is to seamlessly integrate a new hard disk into the existing
volumes, when using striping.

>> Primary issue is speed, but of course (as I have not had a single disk
>> failure save my two ZIP drives which were both broken) data safety would
>> be important as well. I do monthly complete backups (roughly) but I just
>> cannot afford a filesystem slowly corrupting itself.
> For being labeled ALPHA, LVM is awesome.  I haven't had a single LV
> related issue that I can see.

I'll play around with it on my 'playground server'. If I like it, I'll
probably use it. Thanks. :)


-- 
_ciao, Jens_______________________________ http://www.pinguin.conetix.de
    cat /dev/boiler/water | tea | sieve > /cup
    mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp

           reply	other threads:[~1999-02-18 19:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.GHP.4.05.9902161554060.25565-100000@ixion.honeywell.com>]

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=19990218200312.C1529@debian.zuhause.de \
    --to=jens@pinguin.conetix.de \
    --cc=linux-lvm@msede.com \
    --cc=sleas@ixion.honeywell.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