linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Csillag Tamas <cstamas@digitus.itk.ppke.hu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] recovering with missing PV -s
Date: Wed, 21 May 2008 16:54:39 +0200	[thread overview]
Message-ID: <20080521145439.GH3610@digitus> (raw)

Dear lvm list,

We have a DS4700 disk storage system which exports 9 LUNs to a given
machine each one is 1.5TB (because it has 2TB limit on each).
One VG is created from this 9 PV without striping and one LV is built
on it. The filesystem is reiserfs3.

Two days ago one eclosure has failed. 3 PVs out of 9 are missing. The
space usage was about 10%.
Is there a way to recover from this failure with LVM?

Thanks in advance.

Regards,
  cstamas
-- 
CSILLAG Tamas (cstamas) - http://digitus.itk.ppke.hu/~cstamas
Pazmany Peter Catholic University
The Faculty of Information Technology

When hitting yourself on the head with a hammer starts to give you                                  
headaches, the solution is not to put padding on the hammer.

                 reply	other threads:[~2008-05-21 14:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080521145439.GH3610@digitus \
    --to=cstamas@digitus.itk.ppke.hu \
    --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).