Linux LVM users
 help / color / mirror / Atom feed
From: Duane Evenson <devenson@shaw.ca>
To: linux-lvm@sistina.com
Subject: [linux-lvm] vgscan segmentation faults, VG name problems
Date: Sun Apr 27 13:17:01 2003	[thread overview]
Message-ID: <3EAC2003.5030106@shaw.ca> (raw)

I'm having troubles and can't find the solution in the HOWTO, or the 
archived mailing lists articles.
I installed lvm on an entire hard drive (hde), made one logical group 
with a logical volume of 100G.
I mounted to volume, copied files over OK, but vgscan caused 
segmentation faults.
I rebooted, hoping that it was a conflict between the kernel info and 
physical info. Obviously, it wasn't.
Here are the results of running pvdisplay, pvscan, vgscan, and vgdisplay.

# pvdisplay /dev/hde -v
--- Physical volume ---
PV Name               /dev/hde
VG Name               data_group
PV Size               111.79 GB [234441648 secs] / NOT usable 4.25 MB 
[LVM: 239
KB]
PV#                   1
PV Status             available
Allocatable           yes
Cur LV                1
PE Size (KByte)       4096
Total PE              28617
Free PE               3017
Allocated PE          25600
PV UUID               x1l2a2-XUzX-XEjZ-hP3k-qAmo-G5jH-U1z1C8

pvdisplay -- "/etc/lvmtab.d/data_group" doesn't exist

# pvscan -v
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- walking through all physical volumes found
pvscan -- inactive PV "/dev/hde"  is associated to unknown VG 
"data_group" (run
vgscan)
pvscan -- total: 1 [111.79 GB] / in use: 1 [111.79 GB] / in no VG: 0 [0]

# vgscan -v
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- reading data of volume group "data_group" from physical volume(s)
Segmentation fault

# vgscan -d
...
<55555> pv_create_name_from_kdev_t -- LEAVING with dev_name: /dev/hde
<55555> system_id_check_exported -- CALLED
<55555> system_id_check_exported -- LEAVING with ret: 0
<4444> pv_read -- LEAVING with ret: 0
<4444> vg_copy_from_disk -- CALLED
<55555> vg_check_vg_disk_t_consistency -- CALLED
<666666> vg_check_name -- CALLED with VG:
<7777777> lvm_check_chars -- CALLED with name: ""
<7777777> lvm_check_chars -- LEAVING with ret: 0
<666666> vg_check_name -- LEAVING with ret: 0
<55555> vg_check_vg_disk_t_consistency -- LEAVING with ret: -344
<4444> vg_copy_from_disk -- LEAVING
Segmentation fault

# vgdisplay data_group -h
Logical Volume Manager 1.0.3
Heinz Mauelshagen, Sistina Software  19/02/2002 (IOP 10)

vgdisplay -- display volume group information

             reply	other threads:[~2003-04-27 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27 13:17 Duane Evenson [this message]
2003-04-28  4:03 ` [linux-lvm] vgscan segmentation faults, VG name problems Heinz J . Mauelshagen
2003-04-29 20:34   ` [linux-lvm] vgscan problem (was vgscan segmentation faults, VG name problems) Duane Evenson
2003-04-30  6:11     ` Heinz J . Mauelshagen
2003-04-30 21:12       ` Duane Evenson
2003-05-02 22:29         ` [linux-lvm] vgscan problem Duane Evenson
2003-05-06 20:12     ` [linux-lvm] vgcfgrestore -- can't restore part of active volume group "vg01" Duane Evenson

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=3EAC2003.5030106@shaw.ca \
    --to=devenson@shaw.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox