From: jon+lvm@silicide.dk
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] hard disk crash
Date: Thu Oct 31 16:20:03 2002 [thread overview]
Message-ID: <20021031221920.GA26610@gw.silicide.dk> (raw)
In-Reply-To: <Pine.LNX.4.44.0210312035120.26055-100000@server.piarista-kkt.sulinet.hu>
On Thu, Oct 31, 2002 at 08:37:02PM +0100, NagyZ wrote:
[cut]
> i replaced the drive, and pvscan says that VG is OK..
> all LV s could be mounted, except one.
> i run mkreiserfs on this, and from then we're using that..
> thnx for the advice.
you were lucky
> and the boss said: 'for what would you buy new disks? to buy new again
> tomorrow to replace them?' so the answer was no :)
is this a production system ??
If so, i'd suggest you start looking for a new boss, one that gives you
enough money to at least run software raid.
Ask him how much a complete data loss costs ?
Not just your salary for the time you try to recover, but also his
time, and the rest of the workers while the system is down because he
saved money on disk space. And dont get me started about backup.
Remober, if you DO go raid, you NEED to know when a disk goes down,
because if not, you might as well not run raid at all. This means
some sort of management software that keeps an eye on the disks, and
emails you when one fails. Hotswap _MIGHT_ not be needed, but it is
nice.
JonB
prev parent reply other threads:[~2002-10-31 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 9:10 [linux-lvm] hard disk crash NagyZ
2002-10-31 9:22 ` Jon Bendtsen
2002-10-31 9:28 ` NagyZ
2002-10-31 9:36 ` Jon Bendtsen
2002-10-31 10:12 ` NagyZ
2002-10-31 10:18 ` Jon Bendtsen
2002-10-31 11:54 ` Heinz J . Mauelshagen
2002-10-31 12:09 ` NagyZ
2002-10-31 14:33 ` NagyZ
2002-10-31 16:20 ` jon+lvm [this message]
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=20021031221920.GA26610@gw.silicide.dk \
--to=jon+lvm@silicide.dk \
--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.