Linux LVM users
 help / color / mirror / Atom feed
From: lembark@wrkhors.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] getting started with LVM
Date: Thu May 23 15:53:02 2002	[thread overview]
Message-ID: <40970000.1022186992@duke> (raw)
In-Reply-To: <3CED546C.2000401@jumpline.com>


-- Ben Snyder <ben@jumpline.com> on 05/23/02 16:43:24 -0400

> I am currently doing some research for my employer regarding storage and
> backups.  We currently use dump as a backup utility due to limited budget.
> However, dump has been giving us fits due to lseek errors.
> 
> Someone suggested looking into LVM, so here I am.  I looked a the website and
> did a little digging, but I was unable to find out if LVM will serve my
> purposes.
> 
> If anyone can lend a hand and provide feedback that can tell me if LVM is
> worth my effort to solve this problem, or where I can find this sort of
> information, I'd be vert greatful.

Dumping dump might be the first thing that would help. It's
old and tired and deserves a rest... For free utilities you
can get better speed and filtering with cpio, which backs
up from the file system rather than inodes. At that point
LVM is a nice solution for managing anything large enough to
be backed up.

--
Steven Lembark                              2930 W. Palmer
Workhorse Computing                      Chicago, IL 60647
                                           +1 800 762 1582

  reply	other threads:[~2002-05-23 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23 15:46 [linux-lvm] getting started with LVM Ben Snyder
2002-05-23 15:53 ` lembark [this message]
2002-05-23 15:57   ` Ben Snyder
2002-05-23 16:11     ` Lewis Bergman
2002-05-23 21:11     ` Wolfgang Weisselberg
2002-05-24  4:02     ` William Blunn

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=40970000.1022186992@duke \
    --to=lembark@wrkhors.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