All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Data on LVM-Partition, how to read it out
Date: Mon, 20 Aug 2001 11:15:24 +0200	[thread overview]
Message-ID: <20010820111524.A26319@sistina.com> (raw)
In-Reply-To: <20010818133306.A533@btconnect.com>; from thornber@btconnect.com on Sat, Aug 18, 2001 at 01:33:06PM +0100

On Sat, Aug 18, 2001 at 01:33:06PM +0100, Joe Thornber wrote:
> On Sat, Aug 18, 2001 at 02:05:26PM +0200, Alexander Bruns wrote:
> > Resize reiserfs did something but when i wanted to mount the LV it did
> > not work. reiserfs-checks did not found a problem but the mount-binary
> > told my something about a superblock......
> > 
> > 
> > Abter a reboot I now have the following:
> > 
> > [root@holodeck lvmconf]# pvdisplay /dev/hda7
> > pvdisplay
> > --- Physical volume ---
> > PV Name               /dev/hda7
> > VG Name               lvm_volume_01
> > PV Size               48.54 GB / NOT usable 1.06 MB [LVM: 169 KB]
> > PV#                   1
> > PV Status             available
> > Allocatable           yes (but full)
> > Cur LV                1
> > PE Size (KByte)       4096
> > Total PE              12425
> > Free PE               0
> > Allocated PE          12425
> > PV UUID               cFFBJX-aqxr-P7kU-71OY-pgpX-rvtA-XxVpoc
> > 
> > But for /dev/hdb5 and /ev/hdc5 it does not show the same. NOTHING!!
> 
> It looks like you've managed to write over the metadata on the start
> of /dev/hdb5 and /dev/hdc5.  You can confirm this by using the pvdata
> command.  If you have then you will need to restore the metadata from
> a backup, look at vg_cfgrestore.

Small typo here: Joe's refering to vgcfgrestore(8).

> 
> - Joe
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2001-08-20  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18 12:05 [linux-lvm] Data on LVM-Partition, how to read it out Alexander Bruns
2001-08-18 12:33 ` Joe Thornber
2001-08-20  9:15   ` Heinz J . Mauelshagen [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=20010820111524.A26319@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.