From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementationre ady for beta testing
Date: Fri Feb 1 04:18:01 2002 [thread overview]
Message-ID: <20020201111304.C15491@sistina.com> (raw)
In-Reply-To: <20020201110218.B4008@nshhvrnbk013.netshare.ag>; from sgiessler@gmx.net on Fri, Feb 01, 2002 at 11:02:18AM +0100
On Fri, Feb 01, 2002 at 11:02:18AM +0100, STEFANG(GMX) wrote:
> Hallo list,
>
> on Fre, 01 Feb 2002, Heinz J . Mauelshagen (mauelshagen@sistina.com) wrote:
>
> > On Thu, Jan 31, 2002 at 03:05:56PM -0500, Jeff Layton wrote:
> [...]
> > > I've worked with Kevin a few months ago on using EVMS
> > > to recover a filesystem ontop of LVM when a disk went
> > > south and we had no backups
> >
> > It is quite intersting how many people don't take backups even though
> > almost everybody claims to know that backups are crucial and some of them
> > know that they are still, even though they might have RAID in place.
>
> You cannot replace Backups with a RAID system...
Which is exactly my point above ;-)
RAID DOES NOT REPLACE BACKUPS!
> a RAID system is
> just fine to help you in cas of a hardware failure, but if a disk
> driver/user/hacker goes wild you are in big trouble 'cause the data
> is gone on all disks. I had the very same discussion in many
> companies; the MBA guys try to tell you there is no need for a
> backup (Backup is essentially an unneeded "loss center" for them)
> since they have installed a RAID system... ;-)
>
> CU,
> Stefan
> --
> Stefan Giessler e-mail:
> sgiessler@gmx.net
>
> artificial intelligence is no match for natural stupidity
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-02-01 4:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 4:06 [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementationre ady for beta testing STEFANG(GMX)
2002-02-01 4:18 ` Heinz J . Mauelshagen [this message]
2002-02-01 10:02 ` Steven Dake
-- strict thread matches above, loose matches on Subject: below --
2002-02-01 4:26 STEFANG(GMX)
2002-01-31 13:54 [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready " Steve Pratt
2002-01-31 14:05 ` [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementationre ady " Jeff Layton
2002-02-01 3:29 ` Heinz J . Mauelshagen
2002-02-01 9:43 ` Jeff Layton
2002-02-05 8:04 ` James Hawtin
2002-02-05 8:09 ` Patrick Caulfield
2002-02-05 11:13 ` Jesus Manuel NAVARRO LOPEZ
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=20020201111304.C15491@sistina.com \
--to=mauelshagen@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 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.