All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rickard Olsson <richie@webhackande.se>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM1 and a dying disk
Date: Wed Sep  3 05:53:01 2003	[thread overview]
Message-ID: <3F55C7F7.1090305@webhackande.se> (raw)
In-Reply-To: <20030903111442.C2618@sistina.com>

Heinz J . Mauelshagen wrote:

> you say that you don't have a recent LVM metadata backup reflecting
> your VG with /dev/ide/host0/bus1/target0/lun0/disc in it ?

I found a files_vg.conf and put it in /etc/lvmconf, did pvcreate and 
successful vgcfgrestores on all of them. I had to move the disks around 
a bit to make them appear in their old places since they're now in a new 
machine (vgcfgrestore complained otherwise). The bad disk is now at 
/dev/ide/host2/bus1/target1/lun0/disc


majestix root # pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE   PV "/dev/ide/host4/bus1/target0/lun0/disc" of VG "f2" 
       [
149 GB / 0 free]
pvscan -- inactive PV "/dev/ide/host2/bus1/target0/lun0/disc"  is 
associated to
unknown VG "files_vg" (run vgscan)
pvscan -- inactive PV "/dev/ide/host2/bus1/target1/lun0/disc"  is 
associated to
unknown VG "files_vg" (run vgscan)
pvscan -- inactive PV "/dev/ide/host2/bus0/target0/lun0/disc"  is 
associated to
unknown VG "files_vg" (run vgscan)
pvscan -- inactive PV "/dev/ide/host2/bus0/target1/lun0/disc"  is 
associated to
unknown VG "files_vg" (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus1/target0/lun0/disc"  is 
associated to
unknown VG "files_vg" (run vgscan)
pvscan -- inactive PV "/dev/ide/host0/bus1/target1/lun0/disc"  is 
associated to
unknown VG "files_vg" (run vgscan)
pvscan -- total: 7 [819.79 GB] / in use: 7 [819.79 GB] / in no VG: 0 [0]


majestix root # vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "f2"
vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of 
volume
group "files_vg" from physical volume(s)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
groups


majestix root # pvdata /dev/ide/host2/bus1/target1/lun0/disc
--- Physical volume ---
PV Name               /dev/ide/host2/bus1/target1/lun0/disc
VG Name               files_vg
PV Size               93.16 GB [195371568 secs] / NOT usable 16.19 MB 
[LVM: 151
KB]
PV#                   4
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       16384
Total PE              5961
Free PE               0
Allocated PE          5961
PV UUID               KsET9a-qoKI-a2gr-z1GB-jwM1-vFw7-qHgxeZ

--- Volume group ---
VG Name
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               0
MAX LV Size           1023.97 GB
Max PV                256
Cur PV                6
Act PV                6
VG Size               670.61 GB
PE Size               16 MB
Total PE              42919
Alloc PE / Size       42919 / 670.61 GB
Free  PE / Size       0 / 0
VG UUID               Z9MJ9w-UjoI-BO9X-rAb0-DPtF-pXqO-Haiji7

--- List of logical volumes ---

pvdata -- logical volume "/dev/files_vg/files_lv" at offset   0
pvdata -- logical volume struct at offset   1 is empty
[...]


What did I do wrong (this time)?

    / Rickard Olsson,IT-Konsult/
   / Telefon: +46 70 635 01 42/
  / http://www.webhackande.se/

  parent reply	other threads:[~2003-09-03  5:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  3:55 [linux-lvm] LVM1 and a dying disk Rickard Olsson
2003-09-03  4:23 ` Heinz J . Mauelshagen
2003-09-03  4:40   ` Rickard Olsson
2003-09-03  5:53   ` Rickard Olsson [this message]
2003-09-03  7:46     ` Heinz J . Mauelshagen
2003-09-16  6:54       ` [linux-lvm] LVM1 and a dying disk (fixed) Rickard Olsson

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=3F55C7F7.1090305@webhackande.se \
    --to=richie@webhackande.se \
    --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.