linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgchange partial mount fails
Date: Tue, 8 Nov 2005 11:00:23 +0100	[thread overview]
Message-ID: <20051108100023.GA30556@redhat.com> (raw)
In-Reply-To: <436FD150.9080800@oxtel.com>

On Mon, Nov 07, 2005 at 10:12:32PM +0000, Tom Robinson wrote:
> 
> Hi,
> 
> I'm trying to do a partial mount of a VG in order to rescue data from it
> (the last of the 8 PVs has died)
> 
> If I do vgchange -P -a y vg1
> It says:
> 
>  Partial mode. Incomplete volume groups will be activated read-only.
>  7 PV(s) found for VG vg1: expected 8
>  Logical volume (lv1) contains an incomplete mapping table.
>  7 PV(s) found for VG vg1: expected 8
>  Logical volume (lv1) contains an incomplete mapping table.
>  1 logical volume(s) in volume group "vg1" now active
> 
> Which looks like it might have worked, but in /dev/mapper I have:
> 
> crw-rw----  1 root root  10, 63 May 30 02:48 control
> brw-------  1 root root 254,  0 Oct 25 13:20 vg1-lv1
> 
> But I can't mount vg1-lv1 (its ext2 - but it says "must specify fs type).

Looks like expected behaviour.

You're likely missing the beginning of your filesystem which was mapped
to the dead PV and the fs code fails to find its metadata
(ie. superblock).

Check with "lvdisplay -m /dev/vg1/lv1"

Regards,
Heinz    -- The LVM Guy --

> 
> What is wrong? Have I misconfigured lvm / dm?
> are there any lines I need in my config file?
> Are there any tools I can run to get more info?
> 
> The array was built with LVM1 & 2.4.18,
> I'm now using LVM2/DM under 2.6.11.10
> 
> Also, It looks like it has done something, because if I try
> to deactivate it with "vgchange -P -a n vg1" I get:
> 
>  Partial mode. Incomplete volume groups will be activated read-only.
>  7 PV(s) found for VG vg1: expected 8
>  Logical volume (lv1) contains an incomplete mapping table.
>  Can't deactivate volume group "vg1" with 1 open logical volume(s)
> 
> Any help greatly appreciated.
> Kind regards,
> Tom
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
Cluster and Storage Development                   56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2005-11-08 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 22:12 [linux-lvm] vgchange partial mount fails Tom Robinson
2005-11-08 10:00 ` Heinz Mauelshagen [this message]
2005-11-08 11:06   ` Tom Robinson
2005-11-08 12:53     ` Heinz Mauelshagen
2005-11-08 14:24       ` Tom Robinson

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=20051108100023.GA30556@redhat.com \
    --to=mauelshagen@redhat.com \
    --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).