Skip to contentSkip to conversation

LVM and multiple distributions

linux-lvm Shanker Balan 2 participants 4 messages May 21, 2001 – May 24, 2001

lore
Share & tools
lore
#0 lore raw

Hello:

I have been using LVM for some time on RHL 7.0 (with 7.1 updates) and things have been working excellent. LVM is k3wl.

Last week, i installed Debian on a another partition on the same machine and for some odd reason "vgchange -ay" sez "no volume groups found".

godzilla:~# vgchange -ay
vgchange -- no volume groups found

Everything works correctly on RHL. What do i need to do under Debian to get the LVM partition up?

I am using:

Debian Unstable
Kernel 2.4.4 with LVM compiled in
lvm 0.9.1beta7-1

RedHat Linux 7.1
Kernel 2.4.4 with LVM compiled in

Fdisk output:

godzilla:~# fdisk -l /dev/hda|grep -i lvm
/dev/hda8          1803      2185   3076416   8e  Linux LVM

Thanx for your time.

-- Shanu

- - - - - - - - - - - ( Shanu ) - -
Shanker Balan [email protected]

#1 lore raw
Quoted 5 lines · Shanker Balan

Hello:

I have been using LVM for some time on RHL 7.0 (with 7.1 updates) and things have been working excellent. LVM is k3wl.

Quoted 8 lines

Last week, i installed Debian on a another partition on the same machine and for some odd reason "vgchange -ay" sez "no volume groups found".

godzilla:~# vgchange -ay
vgchange -- no volume groups found

Everything works correctly on RHL. What do i need to do under Debian to get the LVM partition up?

Did you run vgscan in order to read the metadata?
"vgchange -ay" afterwards.

Quoted 24 lines

I am using:

Debian Unstable
Kernel 2.4.4 with LVM compiled in
lvm 0.9.1beta7-1

RedHat Linux 7.1
Kernel 2.4.4 with LVM compiled in

Fdisk output:

godzilla:~# fdisk -l /dev/hda|grep -i lvm
/dev/hda8          1803      2185   3076416   8e  Linux LVM

Thanx for your time.

-- Shanu

- - - - - - - - - - - ( Shanu ) - -
Shanker Balan [email protected]
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm

Signature · 15 lines
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
[email protected]                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
#2 lore raw

Hello:

Heinz J. Mauelshagen wrote,

Quoted 2 lines

Did you run vgscan in order to read the metadata?
"vgchange -ay" afterwards.

Yes i did, but does not look like it found something. It does not seem to scan for LVM metadata /dev/hda.

~# vgscan -v -d
<1> lvm_get_iop_version -- CALLED
<22> lvm_check_special -- CALLED
<22> lvm_check_special -- LEAVING
<1> lvm_get_iop_version -- AFTER ioctl ret: 0
<1> lvm_get_iop_version -- LEAVING with ret: 10
<1> lvm_lock -- CALLED
<22> lvm_check_special -- CALLED
<22> lvm_check_special -- LEAVING
<1> lvm_lock -- LEAVING with ret: 0
<1> lvm_dont_interrupt -- CALLED
<1> lvm_dont_interrupt -- LEAVING
<1> lvm_remove_recursive -- CALLED with dir: /etc/lvmtab.d
<1> lvm_remove_recursive -- LEAVING with ret: 0
<1> lvm_tab_create -- CALLED
<22> lvm_tab_write -- CALLED
<22> lvm_tab_write -- LEAVING with ret: 0
<1> lvm_tab_create -- LEAVING with ret: 0
<1> vg_check_exist_all_vg -- CALLED
<22> pv_read_all_pv -- CALLED
<22> pv_read_all_pv -- calling lvm_dir_cache
<333> lvm_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<55555> lvm_check_dev -- CALLED
<55555> lvm_check_dev -- LEAVING with ret: 1
<55555> lvm_dir_cache_hit -- CALLED
<55555> lvm_dir_cache_hit -- LEAVING with ret: 0
<4444> lvm_add_dir_cache -- LEAVING
<4444> lvm_add_dir_cache -- CALLED
<55555> lvm_check_dev -- CALLED
<55555> lvm_check_dev -- LEAVING with ret: 1
<55555> lvm_dir_cache_hit -- CALLED
<55555> lvm_dir_cache_hit -- LEAVING with ret: 1
<4444> lvm_add_dir_cache -- LEAVING
<333> lvm_dir_cache -- LEAVING with ret: 1
<22> pv_read_all_pv -- calling stat with "/dev/hdc"
<333> pv_read -- CALLED with /dev/hdc
<4444> pv_check_name -- CALLED with "/dev/hdc"
<55555> lvm_check_chars -- CALLED with name: "/dev/hdc"
<55555> lvm_check_chars -- LEAVING with ret: 0
<55555> lvm_check_dev -- CALLED
<55555> lvm_check_dev -- LEAVING with ret: 1
<4444> pv_check_name -- LEAVING with ret: 0
<4444> pv_read_already_red -- CALLED with PV /dev/hdc
<4444> pv_read_already_red -- LEAVING with ret: 0
<4444> pv_flush -- CALLED to flush /dev/hdc
<55555> pv_check_name -- CALLED with "/dev/hdc"
<666666> lvm_check_chars -- CALLED with name: "/dev/hdc"
<666666> lvm_check_chars -- LEAVING with ret: 0
<666666> lvm_check_dev -- CALLED
<666666> lvm_check_dev -- LEAVING with ret: 1
<55555> pv_check_name -- LEAVING with ret: 0
<4444> pv_flush -- LEAVING with ret: 0
<333> pv_read -- going to read /dev/hdc
<333> pv_read -- LEAVING with ret: -282
<22> pv_read_all_pv -- pv_read returned: -282
<22> pv_read_all_pv -- avoiding multiple entries in case of MD; np: 0 <22> pv_read_all_pv -- LEAVING with ret: -282
<1> vg_check_exist_all_vg -- LEAVING with 0 VGs
<1> lvm_interrupt -- CALLED
<1> lvm_interrupt -- LEAVING
<1> lvm_unlock -- CALLED
<1> lvm_unlock -- LEAVING with ret: 0
<1> lvm_unlock -- CALLED
<1> lvm_unlock -- LEAVING with ret: -104
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 -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created vgscan -- WARNING: This program does not do a VGDA backup of your volume group

-- Shanu

- - - - - - - - - - - ( Shanu ) - -
Shanker Balan [email protected]

#3 lore raw

Hello:

Sucks, tried everything in the book and still no LVM. I am gonna recreate the LVM partitions from scratch.

Thanx for your time.

-- Shanu

Shanker Balan wrote,

Quoted 2 lines

Yes i did, but does not look like it found something. It does not seem to scan for LVM metadata /dev/hda.

Signature · 2 lines
 -   -   -   -   -   -   -   -   -   -  - ( Shanu )  -  -
 Shanker Balan							[email protected]