linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Removing disk from raid LVM
Date: Tue, 10 Mar 2015 10:05:38 -0400	[thread overview]
Message-ID: <21758.64050.13647.314608@quad.stoffel.home> (raw)
In-Reply-To: <2134825.VZEVSUbKJK@libor-nb>


Libor> web have 4x3TB disks in LVM for backups and I setup per
Libor> customer/per "task" LV type raid5 on it.

Can you post the configuration details please, since they do matter.
It would seem to me, that it would be better to use 'md' to create the
underlying RAID5 device, and then use LVM on top of that /dev/md0 to
create the customer LV(s) as needed.  

Libor> Last week, smartd started to alarm us, that one of the disk
Libor> will soon go away.

Libor> So we shut down the computer, replaced disk and then i used
Libor> vgcfgrestore on new disk to restore metadata.

You should have shutdown the system, added in a new disk, and then
rebooted the system.  At that point you would add the new disk into
the RAID5, and then fail the dying disk.  It would be transparent to
the LVM setup and be much safer.

I'd also strongly advise you to get RAID6 setup and have a hot spare
also setup, so that you don't have this type of issue in the future.  

Libor> Result was, that some LVs came up with damaged filesystem, some
Libor> didn't came up at all with messages like (one of rimage and
Libor> rmeta was "wrong", when i used KVPM util, it was type "virtual"

This sounds very much like you just lost a bunch of data, which RAID5
shouldn't do.  So please post the details of your setup, starting at
the disk level and moving up the stack to the filesystem(s) you have
mounted for backups.  We don't need the customer names, etc, just the
details of the system.

Also, which version of lvm, md, linux kernel, etc are you using?  The
more details the better.

  parent reply	other threads:[~2015-03-10 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 11:21 [linux-lvm] Removing disk from raid LVM Libor Klepáč
2015-03-10  9:23 ` emmanuel segura
2015-03-10  9:34   ` Libor Klepáč
2015-03-10 14:05 ` John Stoffel [this message]
2015-03-11 13:05   ` Libor Klepáč
2015-03-11 15:57     ` John Stoffel
2015-03-11 18:02       ` Libor Klepáč
2015-03-12 14:53         ` John Stoffel
2015-03-12 15:21           ` Libor Klepáč
2015-03-12 17:20             ` John Stoffel
2015-03-12 21:32               ` Libor Klepáč
2015-03-13 16:18                 ` John Stoffel
2015-03-12 15:32           ` Libor Klepáč
2015-03-11 23:12 ` Premchand Gupta

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=21758.64050.13647.314608@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).