All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Lixfeld" <jlixfeld@andromedas.com>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] What have I done!?
Date: Wed, 3 Oct 2001 23:06:24 -0400	[thread overview]
Message-ID: <008f01c14c81$8d300070$836788cf@industry> (raw)
In-Reply-To: <008a01c14c7f$de865e30$836788cf@industry>

Well, because I don't remember what kernel version I was running or what
version of the LVM code I was running, I think me trying to compile
another kernel with the drivers is going to be very much in vein, so I'm
not going to even bother.

Just like the last message:  If anyone can tell me how go about blowing
away the various LVMs so I can try to re-do this thing, I'd appreciate
it!

> -----Original Message-----
> From: linux-lvm-admin@sistina.com 
> [mailto:linux-lvm-admin@sistina.com] On Behalf Of Jason A. Lixfeld
> Sent: October 3, 2001 10:54 PM
> To: linux-lvm@sistina.com
> Subject: [linux-lvm] What have I done!?
> 
> 
> 
> 
> I was running some kernel version (but I forget which one 
> because I deleted it! :/  Now, I'm running 2.4.10.  I was 
> running LVM 0.9B7 or B8. Don't remember.  I upgraded to 1.0 
> without checking for backwards compatibility and now my life 
> is a living hell!  I then upgraded to 1.0.1-rc4 in hopes that 
> it would help.  Here's a rundown of my current confusion as a 
> result of my stupidity:
> 
> # /sbin/lvscan
> lvscan -- ERROR: VGDA in kernel and lvmtab are NOT 
> consistent; please run vgscan
> 
> # /sbin/vgscan
> vgscan -- reading all physical volumes (this may take a 
> while...) vgscan -- found active volume group "HiTiSO3" 
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully 
> created vgscan -- WARNING: This program does not do a VGDA 
> backup of your volume group
> 
> (BTW:  whenever I run vgscan, I get these errors all over the 
> place. The drives are for an LV that is in /proc but not in 
> any of the configs! I even deleted the /dev file hoping it 
> would kill it)
> hdj: read_intr: error=0x04 { DriveStatusError }
> hdj: read_intr: status=0x59 { DriveReady SeekComplete 
> DataRequest Error }
> hdj: read_intr: error=0x04 { DriveStatusError }
> hdj: read_intr: status=0x59 { DriveReady SeekComplete 
> DataRequest Error }
> hdl: read_intr: error=0x04 { DriveStatusError }
> hdl: read_intr: status=0x59 { DriveReady SeekComplete 
> DataRequest Error }
> hdl: read_intr: error=0x04 { DriveStatusError }
> hdl: read_intr: status=0x59 { DriveReady SeekComplete 
> DataRequest Error }
> 
> # /sbin/pvscan
> pvscan -- reading all physical volumes (this may take a 
> while...) pvscan -- inactive PV "/dev/hdm"  is in no VG  [76.34 GB]
> pvscan -- ACTIVE   PV "/dev/hdn1" of VG "foo3" [76.32 GB / 0 free]
> pvscan -- inactive PV "/dev/hdi"  is in no VG  [76.34 GB]
> pvscan -- ACTIVE   PV "/dev/hdg1" of VG "foo3" [76.33 GB / 0 free]
> pvscan -- inactive PV "/dev/hde"  is in no VG  [4.50 MB]
> pvscan -- total: 5 [305.34 GB] / in use: 2 [152.66 GB] / in 
> no VG: 3 [152.67 GB]
> 
> # cat /proc/lvm/global
> LVM driver LVM version 1.0.1-rc4(03/10/2001)
> 
> Total:  2 VGs  4 PVs  2 LVs (1 LV open 1 times)
> 
> Global: 1244191 bytes malloced   IOP version: 10   5:22:56 active
> 
> VG:  foo3  [2 PV, 1 LV/1 open]  PE Size: 4096 KB
>   Usage [KB/PE]: 160071680 /39080 total  160071680 /39080 
> used  0 /0 free
>   PVs: [AA] hdn1                  80031744 /19539   80031744 /19539
> 0 /0     
>        [AA] hdg1                  80039936 /19541   80039936 /19541
> 0 /0     
>     LV:  [AWDL  ] FOO3                     160071680 /39080    1x open
> 
> VG:  foo1  [2 PV, 1 LV/0 open]  PE Size: 4096 KB
>   Usage [KB/PE]: 156295168 /38158 total  156295168 /38158 
> used  0 /0 free
>   PVs: [AA] hdj                   78147584 /19079   78147584 /19079
> 0 /0     
>        [AA] hdl                   78147584 /19079   78147584 /19079
> 0 /0     
>     LV:  [AWDL  ] FOO1                  156295168 /38158    close
> 
> # ls /etc/lvmconf
> foo3.conf
> 
> # more /etc/lvmtab
> foo3
> 
> # ls /etc/lvmtab.d/
> foo3
> 
> # /sbin/pvcreate /dev/hdk
> pvcreate -- ERROR: VGDA in kernel and lvmtab are NOT 
> consistent; please run vgscan
> 
> # /sbin/pvdisplay        
> pvdisplay -- ERROR: VGDA in kernel and lvmtab are NOT 
> consistent; please run vgscan
> 
> # /sbin/vgdisplay
> vgdisplay -- ERROR: VGDA in kernel and lvmtab are NOT 
> consistent; please run vgscan
> 
> # /sbin/lvdisplay
> lvdisplay -- ERROR: VGDA in kernel and lvmtab are NOT 
> consistent; please run vgscan
> 
> There's a couple things:
> 
> 1) I deleted everything in /etc/lv* except for anything 
> related to foo3, yet there is another VG, foo1 in /proc.
> 2) I can't remove inactive drives from showing up in pvscan
> 
> Basically, I just want to delete EVERYTHING EXCEPT for foo3.  
> I'm going to try a downgraded kernel with the old programs 
> and the old drivers and see if that makes any difference (I 
> do have all the configs backed up for the VGs that I deleted 
> previously).
> 
> If anyone has some insight on how I can just delete these 
> things and be done with it, I'd appreciate it.  I can't run 
> any vg commands without getting those VGDA consistency 
> errors.  I tried a fix for that which I found on the 
> archives, but that didn't help at all.
> 
> Any info would be greatly appreciated!!
> 
> -JL
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com 
> http://lists.sistina.com/mailman/listinfo/linu> x-lvm
> read the 
> LVM HOW-TO at 
> http://www.sistina.com/lvm/Pages/howto.html
> 

  reply	other threads:[~2001-10-04  3:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 15:30 [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots Paul Jakma
2001-10-03 18:22 ` Paul Jakma
2001-10-03 19:00   ` Paul Jakma
2001-10-03 19:12     ` svetljo
2001-10-03 19:30       ` Andreas Dilger
2001-10-03 19:40         ` svetljo
2001-10-03 19:52           ` Paul Jakma
2001-10-03 20:44             ` svetljo
2001-10-03 19:56         ` Paul Jakma
2001-10-04  0:45         ` Paul Jakma
2001-10-04  2:54           ` [linux-lvm] What have I done!? Jason A. Lixfeld
2001-10-04  3:06             ` Jason A. Lixfeld [this message]
2001-10-04  5:44             ` idsfa
2001-10-04 11:00               ` Jason A. Lixfeld
2001-10-04 11:24                 ` Jason A. Lixfeld
2001-10-04 17:33                   ` Andreas Dilger
2001-10-04 17:57                     ` Steven Lembark
2001-10-05  7:05                       ` Heinz J . Mauelshagen
2001-10-04  3:28           ` [linux-lvm] lvcreate segfault in vg_setup_pointers_for_snapshots Jason A. Lixfeld
2001-10-04  3:33             ` Andreas Dilger
2001-10-04  3:46               ` Jason A. Lixfeld
2001-10-04  6:04                 ` Andreas Dilger
2001-10-04  7:05                   ` Sean Burford
2001-10-04 10:31                   ` Paul Jakma
2001-10-04 11:05                     ` Joe Thornber
2001-10-04 14:51                       ` Paul Jakma
2001-10-04 11:38                   ` Jason A. Lixfeld
2001-10-04 14:01                     ` Jason A. Lixfeld
2001-10-04 14:23                       ` Jason A. Lixfeld
2001-10-04 15:57                         ` Jason A. Lixfeld
2001-10-04 20:12                           ` Goetz Bock
  -- strict thread matches above, loose matches on Subject: below --
2001-10-04  7:06 [linux-lvm] What have I done!? tim

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='008f01c14c81$8d300070$836788cf@industry' \
    --to=jlixfeld@andromedas.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.