* Re: [linux-lvm] Problem
From: Guido Guenther @ 2002-12-26 7:17 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <OFF86F1941.C6845D82-ON48256C9B.00297D99-48256C9B.00298FD5@ussmy>
On Thu, Dec 26, 2002 at 03:33:46PM +0800, nellis@unionswitch.com.my wrote:
> I'm not sure what going on here . I want to setup my backup server using
> LVM . I have two physical HDD named hda1 ( Linux native ) = 9.5GB , hda2 (
> Linux swap ) = 500MB and hdd1( LVM == 8e ) . I have error that looks like
> this :
>
> root@backupmy:/LVM# ./configure
> loading cache ./config.cache
> checking for mawk... mawk
> checking for gcc... gcc
> checking whether the C compiler (gcc ) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
Something with you C compiler is wrong, see config.log for details.
Can't you use the precompiled lvm that comes with your distribution?
-- Guido
^ permalink raw reply
* [linux-lvm] Problem
From: nellis @ 2002-12-26 1:34 UTC (permalink / raw)
To: linux-lvm
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Hi there ,
I'm not sure what going on here . I want to setup my backup server using
LVM . I have two physical HDD named hda1 ( Linux native ) = 9.5GB , hda2 (
Linux swap ) = 500MB and hdd1( LVM == 8e ) . I have error that looks like
this :
root@backupmy:/LVM# ./configure
loading cache ./config.cache
checking for mawk... mawk
checking for gcc... gcc
checking whether the C compiler (gcc ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
Before that , I can't insmod lvm-mod . I read your docu for a whole day
and give it a try but still no avail . PLEASE HELP .
Regards ,
Nurulhadi Ellis
Union Switch & Signal (M) Sdn Bhd
1903 - 1912 , 19th Floor , Plaza Pengkalan , Jalan Ipoh
51100 Kuala Lumpur
MALAYSIA
Ph : +6 03 4045 8055
Fax : +6 03 4045 8970
[-- Attachment #2: Type: text/html, Size: 1300 bytes --]
^ permalink raw reply
* [linux-lvm] LVM disk problem
From: Skliarouk Arie @ 2002-12-25 3:22 UTC (permalink / raw)
To: linux-lvm
Hello All,
An computer has LVM installed.
The physical volume where an LV is residing developed several bad sectors.
reiserfsck does not (yet) have flag of checking,detecting and marking bad
sectors on disk as such.
Is there a way to tell to LVM to scan the physical volume and mark stripes
(mine are 8MB each) that have bad blocks as unusable ones and move the
stripes to other areas of the disk?
---
Bye, | Fax: (972)-2-6796453
Arieh | Phone: (972)-6795364
^ permalink raw reply
* Re: [linux-lvm] Merry Christmas
From: grobe @ 2002-12-24 9:40 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20021224125721.A21501@sistina.com>
Schoene Weihnachten, guten Rutsch und viele Gruesse!
CU Lars.
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr f�r 1 ct/ Min. surfen!
^ permalink raw reply
* [linux-lvm] Merry Christmas
From: Heinz J . Mauelshagen @ 2002-12-24 6:07 UTC (permalink / raw)
To: linux-lvm
Merry Christmas to you all :-)
Enjoy a great, peaceful time with your families and friends.
Warm regards,
Heinz -- The LVM Guy --
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply
* Re: [linux-lvm] broken computer
From: Anders Widman @ 2002-12-24 4:46 UTC (permalink / raw)
To: FRANK VAN DAMME; +Cc: linux-lvm
In-Reply-To: <33334750984.20021224114437@tnonline.net>
> Hello,
> I have a quick question. I have been running lvm on my system for a while, it
> works very good. However, the motherbord is wearing and the thing refuses to
> boot. Can I, if I put my hard disk in another system, mount the lvm volumes on
> it? I need my data right now...
> Normally the drive is on hda, but it will certainly have another adresse in my
> other box, since I only have athlon-optimised kernels on the faulty box and
> the only other useable machine I have is a p133, which has to boot from a
> smaller disk (1024 cylinder limit you see). My root filesystem is not in the
> lvm volume.
LVM can mount volumes even if the harddrives have changed order.
> Frank
> P.S. I am NOT on the LVM mailing list, so could you please CC me? Thanks.
^ permalink raw reply
* Re: [linux-lvm] broken computer
From: Anders Widman @ 2002-12-24 4:45 UTC (permalink / raw)
To: FRANK VAN DAMME
In-Reply-To: <1040726414.3e08398e92f76@webmail.kuleuven.ac.be>
> Hello,
> I have a quick question. I have been running lvm on my system for a while, it
> works very good. However, the motherbord is wearing and the thing refuses to
> boot. Can I, if I put my hard disk in another system, mount the lvm volumes on
> it? I need my data right now...
> Normally the drive is on hda, but it will certainly have another adresse in my
> other box, since I only have athlon-optimised kernels on the faulty box and
> the only other useable machine I have is a p133, which has to boot from a
> smaller disk (1024 cylinder limit you see). My root filesystem is not in the
> lvm volume.
LVM can mount volumes even if the harddrives have changed order.
> Frank
> P.S. I am NOT on the LVM mailing list, so could you please CC me? Thanks.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
^ permalink raw reply
* [linux-lvm] broken computer
From: FRANK VAN DAMME @ 2002-12-24 4:40 UTC (permalink / raw)
To: linux-lvm
Hello,
I have a quick question. I have been running lvm on my system for a while, it
works very good. However, the motherbord is wearing and the thing refuses to
boot. Can I, if I put my hard disk in another system, mount the lvm volumes on
it? I need my data right now...
Normally the drive is on hda, but it will certainly have another adresse in my
other box, since I only have athlon-optimised kernels on the faulty box and
the only other useable machine I have is a p133, which has to boot from a
smaller disk (1024 cylinder limit you see). My root filesystem is not in the
lvm volume.
Frank
P.S. I am NOT on the LVM mailing list, so could you please CC me? Thanks.
^ permalink raw reply
* Re: [linux-lvm] vgcreate bug?
From: NagyZ @ 2002-12-23 17:05 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20021223224907.A20127@uk.sistina.com>
On Mon, 23 Dec 2002, Alasdair G Kergon wrote:
> On Mon, Dec 23, 2002 at 07:34:35PM +0100, NagyZ wrote:
> > vgchange -an
> > and (with lvm2 tools):
> > vgconvert -M2 test
>
> Missing vgchange -ay (with LVM2 tools) here?
that doesnt matter :)
>
> > then:
> > debian:~# mount /dev/test/testlv /teszt
> > mount: /dev/test/testlv is not a valid block device
>
> [It's possible the problem is with LVM1 volume group links in /dev left behind
> by LVM1; if so, just remove them before the LVM2 vgchange -ay; this is
> libdevmapper being ultra-cautious; will get changed soon.]
yes..
i tested again:
after the convert i did rm /dev/test -Rf, then vgchange -ay, and WORKS! :)
thnx
NagyZ
^ permalink raw reply
* Re: [linux-lvm] vgcreate bug?
From: Alasdair G Kergon @ 2002-12-23 16:49 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <Pine.LNX.4.44.0212231927280.31788-100000@server.piarista-kkt.sulinet.hu>
On Mon, Dec 23, 2002 at 07:34:35PM +0100, NagyZ wrote:
> vgchange -an
> and (with lvm2 tools):
> vgconvert -M2 test
Missing vgchange -ay (with LVM2 tools) here?
> then:
> debian:~# mount /dev/test/testlv /teszt
> mount: /dev/test/testlv is not a valid block device
[It's possible the problem is with LVM1 volume group links in /dev left behind
by LVM1; if so, just remove them before the LVM2 vgchange -ay; this is
libdevmapper being ultra-cautious; will get changed soon.]
Alasdair
--
agk@uk.sistina.com
^ permalink raw reply
* Re: [linux-lvm] vgcreate bug?
From: NagyZ @ 2002-12-23 14:07 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20021223200006.GB18720@tykepenguin.com>
On Mon, 23 Dec 2002, Patrick Caulfield wrote:
> On Mon, Dec 23, 2002 at 07:34:35PM +0100, NagyZ wrote:
>
> This is a vgconvert bug isn't is ?
>
i wanted to write that :)
NagyZ
^ permalink raw reply
* Re: [linux-lvm] vgcreate bug?
From: Patrick Caulfield @ 2002-12-23 13:59 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <Pine.LNX.4.44.0212231927280.31788-100000@server.piarista-kkt.sulinet.hu>
On Mon, Dec 23, 2002 at 07:34:35PM +0100, NagyZ wrote:
This is a vgconvert bug isn't is ?
patrick
^ permalink raw reply
* [linux-lvm] vgcreate bug?
From: NagyZ @ 2002-12-23 12:28 UTC (permalink / raw)
To: linux-lvm
so..
i did:
(with 1.0.6 tools)
dd if=/dev/zero of=/testlvmimage bs=1024k count=300
losetup /dev/loop0 /testlvmimage
pvcreate /dev/loop
vgcreate test /dev/loop0
lvcreate -l 8 -n testlv test
mkfs.ext3 /dev/test/testlv
then copy some files..
vgchange -an
and (with lvm2 tools):
vgconvert -M2 test
then:
debian:~# mount /dev/test/testlv /teszt
mount: /dev/test/testlv is not a valid block device
so..
any idea? :)
check http://tom.tdc.hu/~nagyz/lvm
thnx!
NagyZ
^ permalink raw reply
* Re: [linux-lvm] upgrading..
From: Patrick Caulfield @ 2002-12-23 10:54 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <Pine.LNX.4.44.0212231717400.31560-100000@server.piarista-kkt.sulinet.hu>
On Mon, Dec 23, 2002 at 05:19:01PM +0100, NagyZ wrote:
> hi!
>
> i did some test last night at my test machine..
> i upgraded my vg from 1.0.6 to last lvm2+dm..
> after the upgrade, i cant mount my lv's..
> is this a bug? or i wont be able to use my data after upgrade?..
Sounds odd to me. I regularly flip between LVM1 and LVM2.
--
patrick
^ permalink raw reply
* [linux-lvm] upgrading..
From: NagyZ @ 2002-12-23 10:13 UTC (permalink / raw)
To: linux-lvm
hi!
i did some test last night at my test machine..
i upgraded my vg from 1.0.6 to last lvm2+dm..
after the upgrade, i cant mount my lv's..
is this a bug? or i wont be able to use my data after upgrade?..
NagyZ
^ permalink raw reply
* Re: [linux-lvm] VFS Locking Patch for 2.4.20? 2.4.19 does not work
From: Goetz Bock @ 2002-12-21 19:54 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20021216141212.GE869@tykepenguin.com>
On Mon, Dec 16 '02 at 14:12, Patrick Caulfield wrote:
> > is there anywhere a VFS locking patch for kernel version 2.4.20? The
> > latest LVM1-release only includes the one for 2.4.19.
> The 2.4.19 one should work just fine.
As you might know 2.4.20 has a filesystem corruption bug with ext3 fs.
Unforunately the patch changes the semantic of sync_supers by adding a
parameter "wait".
I've not enough knowledge of how the VFS works to dear to update the
patch ... did anyone already do this?
BTW: the ext3 patches are available from
http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.20/
--
Goetz Bock (c) 2002 as blacknet.de - Munich - Germany /"\
IT Consultant GNU FDL 1.1 secure mobile Linux everNETting \ /
X
ASCII Ribbon Campaign against HTML email & microsoft attachments / \
^ permalink raw reply
* [linux-lvm] help! system crash ...
From: Bill Wester @ 2002-12-21 11:59 UTC (permalink / raw)
To: linux-lvm
[-- Attachment #1: Type: text/plain, Size: 11745 bytes --]
Hi everyone it seems im in a pinch.
my system crashed last night... system disk dead! So i replaced it, unfortunately i lost all of the /etc/lvm data.
I rebuilt my system.. (RH 8.0) and it seemed to go well. For some reason when i try to bring my LVM back up it croaks and dies.
Here is the output... it looks like somehow /dev/hdc got messed up and has no PE's on it anymore. How can i get it back? Remember i dont have any of the backups because my system hard drive was wasted!
can i just re-create it? it was just one big disk, with a very simple layout. How can i do that and keep the integrity of the other PV's?
any help would be VERY appreciated...
bill
<<55555> lvm_check_uuid -- LEAVING with ret: -1
<55555> lvm_check_uuid -- CALLED with uuidstr: ""
<55555> lvm_check_uuid -- LEAVING with ret: -1
<4444> pv_read_uuidlist -- LEAVING with ret: 4
<333> pv_read_all_pv_of_vg -- LEAVING with ret: 0
<22> vg_read -- pv[0]->pv_name: "/dev/hdg"
<22> vg_read -- pv[1]->pv_name: "/dev/hde1"
<22> vg_read -- pv[2]->pv_name: "/dev/hdc"
<22> vg_read -- pv[3]->pv_name: "/dev/hdd"
<333> vg_read_from_pv -- CALLED
<4444> pv_check_name -- CALLED with "/dev/hdg"
<55555> lvm_check_chars -- CALLED with name: "/dev/hdg"
<55555> lvm_check_chars -- LEAVING with ret: 0
<4444> pv_check_name -- LEAVING with ret: 0
<4444> pv_read -- CALLED with /dev/hdg
<55555> pv_check_name -- CALLED with "/dev/hdg"
<666666> lvm_check_chars -- CALLED with name: "/dev/hdg"
<666666> lvm_check_chars -- LEAVING with ret: 0
<55555> pv_check_name -- LEAVING with ret: 0
<4444> pv_read -- going to read /dev/hdg
<55555> lvm_check_dev -- CALLED
<666666> lvm_check_partitioned_dev -- CALLED
<7777777> lvm_get_device_type called
<7777777> lvm_get_device_type leaving with 0
<666666> lvm_check_partitioned_dev -- LEAVING with ret: TRUE
<55555> lvm_check_dev -- LEAVING with ret: 1
<55555> pv_copy_from_disk -- CALLED
<55555> pv_copy_from_disk -- LEAVING ret = 0x804d088
<55555> pv_create_name_from_kdev_t -- CALLED with 34:0
<666666> lvm_check_dev -- CALLED
<7777777> lvm_check_partitioned_dev -- CALLED
<88888888> lvm_get_device_type called
<88888888> lvm_get_device_type leaving with 0
<7777777> lvm_check_partitioned_dev -- LEAVING with ret: TRUE
<666666> lvm_check_dev -- LEAVING with ret: 1
<666666> lvm_dir_cache -- CALLED
<666666> lvm_dir_cache -- LEAVING with ret: 17
<55555> pv_create_name_from_kdev_t -- LEAVING with dev_name: /dev/hdg
<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: 0
<4444> vg_copy_from_disk -- LEAVING
<333> vg_read_from_pv -- LEAVING with ret: 0
<22> vg_read -- LEAVING with ret: 0
<1> vg_read_with_pv_and_lv -- AFTER vg_read; vg_this->lv_cur: 1
<22> pv_read_all_pv_of_vg -- CALLED with vg_name: "hotline"
<333> vg_check_name -- CALLED with VG: hotline
<4444> lvm_check_chars -- CALLED with name: "hotline"
<4444> lvm_check_chars -- LEAVING with ret: 0
<333> vg_check_name -- LEAVING with ret: 0
<22> pv_read_all_pv_of_vg -- LEAVING with ret: 0
<1> vg_read_with_pv_and_lv -- AFTER pv_read_all_pv_of_vg
<22> pv_read_all_pe_of_vg -- CALLED
<333> vg_check_name -- CALLED with VG: hotline
<4444> lvm_check_chars -- CALLED with name: "hotline"
<4444> lvm_check_chars -- LEAVING with ret: 0
<333> vg_check_name -- LEAVING with ret: 0
<333> pv_read_all_pv_of_vg -- CALLED with vg_name: "hotline"
<4444> vg_check_name -- CALLED with VG: hotline
<55555> lvm_check_chars -- CALLED with name: "hotline"
<55555> lvm_check_chars -- LEAVING with ret: 0
<4444> vg_check_name -- LEAVING with ret: 0
<333> pv_read_all_pv_of_vg -- LEAVING with ret: 0
<22> pv_read_all_pe_of_vg -- pv_count: 4
<333> pv_read_pe -- CALLED with /dev/hdg and 3052
<4444> pe_copy_from_disk -- CALLED
<4444> pe_copy_from_disk -- LEAVING
<333> pv_read_pe -- ret: 0
<333> pv_read_pe -- LEAVING with ret: 0
<22> pv_read_all_pe_of_vg -- /dev/hdg with 3052 PE at address 804F078
<333> pv_read_pe -- CALLED with /dev/hde1 and 2383
<4444> pe_copy_from_disk -- CALLED
<4444> pe_copy_from_disk -- LEAVING
<333> pv_read_pe -- ret: 0
<333> pv_read_pe -- LEAVING with ret: 0
<22> pv_read_all_pe_of_vg -- /dev/hde1 with 2383 PE at address 804F07C
<333> pv_read_pe -- CALLED with /dev/hdc and 0
<4444> pe_copy_from_disk -- CALLED
<4444> pe_copy_from_disk -- LEAVING
<333> pv_read_pe -- ret: 0
<333> pv_read_pe -- LEAVING with ret: 0
<22> pv_read_all_pe_of_vg -- /dev/hdc with 0 PE at address 804F080
<333> pv_read_pe -- CALLED with /dev/hdd and 2441
<4444> pe_copy_from_disk -- CALLED
<4444> pe_copy_from_disk -- LEAVING
<333> pv_read_pe -- ret: 0
<333> pv_read_pe -- LEAVING with ret: 0
<22> pv_read_all_pe_of_vg -- /dev/hdd with 2441 PE at address 804F084
<22> pv_read_all_pe_of_vg -- AFTER LOOP of pv_read_pe
<22> pv_read_all_pe_of_vg -- /dev/hdg with 3052 PE at 805D960 for PV #0
<22> pv_read_all_pe_of_vg -- /dev/hde1 with 2383 PE at 8060918 for PV #1
<22> pv_read_all_pe_of_vg -- /dev/hdc with 0 PE at 0 for PV #2 <-----------------------------PROBLEM!!!
<22> pv_read_all_pe_of_vg -- /dev/hdd with 2441 PE at 8062E58 for PV #3
<22> pv_read_all_pe_of_vg -- LEAVING with ret: 0
<1> vg_read_with_pv_and_lv -- AFTER pv_read_all_pe_of_vg
<22> lv_read_all_lv -- CALLED
<333> vg_check_name -- CALLED with VG: hotline
<4444> lvm_check_chars -- CALLED with name: "hotline"
<4444> lvm_check_chars -- LEAVING with ret: 0
<333> vg_check_name -- LEAVING with ret: 0
<333> vg_read -- CALLED
<4444> vg_check_name -- CALLED with VG: hotline
<55555> lvm_check_chars -- CALLED with name: "hotline"
<55555> lvm_check_chars -- LEAVING with ret: 0
<4444> vg_check_name -- LEAVING with ret: 0
<4444> pv_read_all_pv_of_vg -- CALLED with vg_name: "hotline"
<55555> vg_check_name -- CALLED with VG: hotline
<666666> lvm_check_chars -- CALLED with name: "hotline"
<666666> lvm_check_chars -- LEAVING with ret: 0
<55555> vg_check_name -- LEAVING with ret: 0
<4444> pv_read_all_pv_of_vg -- LEAVING with ret: 0
<333> vg_read -- pv[0]->pv_name: "/dev/hdg"
<333> vg_read -- pv[1]->pv_name: "/dev/hde1"
<333> vg_read -- pv[2]->pv_name: "/dev/hdc"
<333> vg_read -- pv[3]->pv_name: "/dev/hdd"
<4444> vg_read_from_pv -- CALLED
<55555> pv_check_name -- CALLED with "/dev/hdg"
<666666> lvm_check_chars -- CALLED with name: "/dev/hdg"
<666666> lvm_check_chars -- LEAVING with ret: 0
<55555> pv_check_name -- LEAVING with ret: 0
<55555> pv_read -- CALLED with /dev/hdg
<666666> pv_check_name -- CALLED with "/dev/hdg"
<7777777> lvm_check_chars -- CALLED with name: "/dev/hdg"
<7777777> lvm_check_chars -- LEAVING with ret: 0
<666666> pv_check_name -- LEAVING with ret: 0
<55555> pv_read -- going to read /dev/hdg
<666666> lvm_check_dev -- CALLED
<7777777> lvm_check_partitioned_dev -- CALLED
<88888888> lvm_get_device_type called
<88888888> lvm_get_device_type leaving with 0
<7777777> lvm_check_partitioned_dev -- LEAVING with ret: TRUE
<666666> lvm_check_dev -- LEAVING with ret: 1
<666666> pv_copy_from_disk -- CALLED
<666666> pv_copy_from_disk -- LEAVING ret = 0x804f0a8
<666666> pv_create_name_from_kdev_t -- CALLED with 34:0
<7777777> lvm_check_dev -- CALLED
<88888888> lvm_check_partitioned_dev -- CALLED
<999999999> lvm_get_device_type called
<999999999> lvm_get_device_type leaving with 0
<88888888> lvm_check_partitioned_dev -- LEAVING with ret: TRUE
<7777777> lvm_check_dev -- LEAVING with ret: 1
<7777777> lvm_dir_cache -- CALLED
<7777777> lvm_dir_cache -- LEAVING with ret: 17
<666666> pv_create_name_from_kdev_t -- LEAVING with dev_name: /dev/hdg
<666666> system_id_check_exported -- CALLED
<666666> system_id_check_exported -- LEAVING with ret: 0
<55555> pv_read -- LEAVING with ret: 0
<55555> vg_copy_from_disk -- CALLED
<666666> vg_check_vg_disk_t_consistency -- CALLED
<7777777> vg_check_name -- CALLED with VG:
<88888888> lvm_check_chars -- CALLED with name: ""
<88888888> lvm_check_chars -- LEAVING with ret: 0
<7777777> vg_check_name -- LEAVING with ret: 0
<666666> vg_check_vg_disk_t_consistency -- LEAVING with ret: 0
<55555> vg_copy_from_disk -- LEAVING
<4444> vg_read_from_pv -- LEAVING with ret: 0
<333> vg_read -- LEAVING with ret: 0
<22> lv_read_all_lv -- lv_max: 256
<22> lv_read_all_lv -- BEFORE pv_read_all_pv_of_vg
<333> pv_read_all_pv_of_vg -- CALLED with vg_name: "hotline"
<4444> vg_check_name -- CALLED with VG: hotline
<55555> lvm_check_chars -- CALLED with name: "hotline"
<55555> lvm_check_chars -- LEAVING with ret: 0
<4444> vg_check_name -- LEAVING with ret: 0
<333> pv_read_all_pv_of_vg -- LEAVING with ret: 0
<333> lv_copy_from_disk -- CALLED
<333> lv_copy_from_disk -- LEAVING
<22> lv_read_all_lv -- l: 256 nl: 1 vg_this->lv_cur: 1
<22> lv_read_all_lv -- LEAVING with ret: 0
<1> vg_read_with_pv_and_lv -- AFTER lv_read_all_lv; vg_this->pv_cur: 4 vg_this-
>pv_max: 256 ret: 0
<1> vg_read_with_pv_and_lv -- BEFORE for PE
<1> vg_read_with_pv_and_lv -- AFTER for PE
<1> vg_read_with_pv_and_lv -- BEFORE for LV
<1> vg_read_with_pv_and_lv -- vg_this->lv[0]->lv_allocated_le: 11180
vgscan -- only found 7518 of 11180 LEs for LV /dev/hotline/vol1 (0)
<1> vg_read_with_pv_and_lv -- LEAVING with ret: -365
<1> lvm_error -- CALLED with: -365
<1> lvm_error -- LEAVING with: "vg_read_with_pv_and_lv(): allocated LE of LV"
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get data of
volume group "hotline" from physical volume(s)
<1> vg_free -- CALLED
<1> vg_free -- LEAVING with ret: -99
<1> lvm_interrupt -- CALLED
<1> lvm_interrupt -- LEAVING
<1> lvm_unlock -- CALLED
<1> lvm_unlock -- LEAVING with ret: 0
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume group
<1> lvm_unlock -- CALLED
<1> lvm_unlock -- LEAVING with ret: -104
[root@blackbird root]#
[root@blackbird root]# pvdata /dev/hdc
--- NEW Physical volume ---
PV Name /dev/hdc
VG Name hotline
PV Size 30.94 MB [63360 secs]
PV# 3
PV Status available
Allocatable NO
Cur LV 0
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID s8Gp0j-WWq2-yT9m-UnCz-qU7m-TnCG-tHwVaI
--- 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 2 TB
Max PV 256
Cur PV 4
Act PV 4
VG Size 360.56 GB
PE Size 32 MB
Total PE 11538
Alloc PE / Size 11180 / 349.38 GB
Free PE / Size 358 / 11.19 GB
VG UUID snZQHp-EWmO-aeox-1Cbi-8Guy-UPaU-l4UdJm
--- List of logical volumes ---
pvdata -- logical volume "/dev/hotline/vol1" at offset 0
pvdata -- logical volume struct at offset 1 is empty
...
pvdata -- logical volume struct at offset 255 is empty
--- List of physical volume UUIDs ---
001: ZLU9xB-hy6U-I7UF-Fd9C-3lTW-wKMX-9nhxcY
002: UGmBIH-LfYd-JQdV-xT2A-oSqj-8prs-ezsRLO
003: s8Gp0j-WWq2-yT9m-UnCz-qU7m-TnCG-tHwVaI
004: MFAGC5-zznc-n0xn-T5rT-Cluh-b9qR-6v7oge
[root@blackbird root]#
[-- Attachment #2: Type: text/html, Size: 17259 bytes --]
^ permalink raw reply
* Re: [linux-lvm] Re: RH8 install - LVM sizing problem
From: grenoml @ 2002-12-21 10:33 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20021218215632.405.qmail@web14407.mail.yahoo.com>
I checked the /var/log/boot.log and vgscan was working fine during
bootup so I thought about it for a second and realized that these
commands must require being run as 'root'. So I did a 'su -' and tried
both commands and they worked fine. I didn't see any mention of this
in the man pages and the errors that were thrown were rather cryptic.
My preference is that commands requiring certain user or authority
should either work completely or not work at all and provide the user
with a good hint as to why.
Regards,
Gerry Reno
--- grenoml <grenoml@yahoo.com> wrote:
> An update to the problem:
> I finally reinstalled RH8 and made the following adjustments:
> -pulled / out of LVM and put in its own partition
> -increased both the size of / (5G) and /usr (15G)
>
> An 'everything' installation went fine this time with the only
> problem being it was trying to run kudzu on the first reboot and when
> it came up I had no mouse or keyboard so I rebooted and everything
> was
> fine after that and so I finished the Setup config and Linux went to
> the first login screen. Once logged in I went to a terminal window
> and
> ran pvdisplay and vgscan and received the exact same response as
> after
> the first installation:
>
> + /sbin/pvdisplay
> pvdisplay -- ERROR: "/etc/lvmtab" doesn't exist; please run vgscan
>
> + /sbin/vgscan
> vgscan -- LVM driver/module not loaded?
>
> So my question is what should I do to verify the state of LVM on the
> system?
>
> Regards,
> Gerry Reno
>
>
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
^ permalink raw reply
* [linux-lvm] Operation Not Permitted on 2.4.20
From: Tren Blackburn @ 2002-12-19 11:06 UTC (permalink / raw)
To: linux-lvm
Hi all;
I've done some searching on the list and the closest I can come up with
is this:
http://lists.sistina.com/pipermail/lvm-devel/2002-March/000873.html
This is a new NetFinity server, hardware RAID 5 array. I partitioned
the drive, set up a second partition as Linux LVM. Linux kernel is
2.4.20 and LVM version is 1.1-rc2 (kernel patched with this as well)
Ran pvcreate which worked fine
Ran vgcreate which worked fine
Ran lvcreate -L1G -nlvusr rootvg which gave:
lvcreate -- ERROR "Operation not permitted" opening logical volume
"/dev/rootvg/lvusr"
Running lvremove /dev/rootvg/lvusr gives:
lvremove -- ERROR "lv_release(): LV number" releasing logical volume
"/dev/rootvg/lvusr"
And if I try to build a filesystem on this LV I get:
count_blocks: open failed (Operation not permitted)
If I run vgscan -f I can remove the lv properly, but I cannot create a
filesystem still (get same error) What can I give in the way of debug
output to be helpful here. Is anyone else experiencing this problem?
Regards,
Tren
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- Tren Blackburn - Owner mailto:tren@eotnetworks.com =
= EOT Networks http://www.eotnetworks.com -
- Phone (403) 818-7658 Fax (403) 269-2122 =
= ** Infinite Solutions for a Finite World ** -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
------------------------------------------------------------------------
DISCLAIMER: This e-mail message is intended only for the named
recipient(s) above and may contain information that is privileged,
confidential and/or exempt from disclosure under applicable law. If you
have received this message in error, or are not the named recipient(s),
please immediately notify the sender and delete this e-mail message.
------------------------------------------------------------------------
^ permalink raw reply
* Re: [linux-lvm] LVM and ext3
From: Goetz Bock @ 2002-12-19 10:53 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAd/KEPwmKaEO7gaS5NXV+c+KAAAAQAAAAlydtpuHoQkO4QgscMTdYbgEAAAAA@freestylenetworks.com>
On Thu, Dec 19 '02 at 09:30, Paul Seniuk wrote:
> Is there support for ext3 partion resizing?
do it all the time (growing). there is even a special tool to support
that with just one call to enlagre the LV and then the ext2/3
filesystem: e2fsadm
> (RH 7.3)?
no idea about that. but no problems with TSL1.5 (own patches) and TSL20
should work out of the box (I'll work on it, except for the installer)
--
Goetz Bock (c) 2002 as blacknet.de - Munich - Germany /"\
IT Consultant GNU FDL 1.1 secure mobile Linux everNETting \ /
X
ASCII Ribbon Campaign against HTML email & microsoft attachments / \
^ permalink raw reply
* [linux-lvm] LVM and ext3
From: Paul Seniuk @ 2002-12-19 10:31 UTC (permalink / raw)
To: linux-lvm
Hello,
Is there support for ext3 partion resizing? (RH 7.3)?
Paul Seniuk
Freestyle Networks
v: 780-919-3629
^ permalink raw reply
* Re: [linux-lvm] lvm2 + 2.4.20
From: Joe Thornber @ 2002-12-19 3:08 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <Pine.LNX.4.44.0212190026320.11789-100000@server.piarista-kkt.sulinet.hu>
On Thu, Dec 19, 2002 at 12:28:18AM +0100, NagyZ wrote:
> hi!
>
> i wondering.. there will be an other dm patchet for this kernel as like
> for 2.5 ?
There will be more patchsets for the 2.4 kernel at some point.
However there is nothing critical on the list of changes, don't be
afraid to use the current patchset.
> how much time does take to upgrade my lvm1 metadata to lvm2?
> i have 1T+ data..
> ( i dont have a couple of hours.. max. 15-30 minutes )
I'll leave Alasdair to answer this one ...
- Joe
^ permalink raw reply
* [linux-lvm] PV Resizing
From: Monty Taylor @ 2002-12-18 22:57 UTC (permalink / raw)
To: linux-lvm
Hello.
I've managed to get myself into a rather funny spot -- I use LVM to
provide administrative flexibility, but I didn't account for one
possibility. I'm hoping someone has an idea...
I have a machine with a single hard drive. I have three partitions,
boot, swap, and the lvm partition. I now need to install a windows
partition... (damn CAD program won't run under WINE) Is there _any_ way
to resize the PV from under LVM? (Like with parted or something) so I
can create another partition?
Thanks in advance.
Monty
^ permalink raw reply
* [linux-lvm] lvm2 + 2.4.20
From: NagyZ @ 2002-12-18 17:23 UTC (permalink / raw)
To: linux-lvm
hi!
i wondering.. there will be an other dm patchet for this kernel as like
for 2.5 ?
how much time does take to upgrade my lvm1 metadata to lvm2?
i have 1T+ data..
( i dont have a couple of hours.. max. 15-30 minutes )
NagyZ
^ permalink raw reply
* [linux-lvm] Re: RH8 install - LVM sizing problem
From: grenoml @ 2002-12-18 15:56 UTC (permalink / raw)
To: linux-lvm
An update to the problem:
I finally reinstalled RH8 and made the following adjustments:
-pulled / out of LVM and put in its own partition
-increased both the size of / (5G) and /usr (15G)
An 'everything' installation went fine this time with the only
problem being it was trying to run kudzu on the first reboot and when
it came up I had no mouse or keyboard so I rebooted and everything was
fine after that and so I finished the Setup config and Linux went to
the first login screen. Once logged in I went to a terminal window and
ran pvdisplay and vgscan and received the exact same response as after
the first installation:
+ /sbin/pvdisplay
pvdisplay -- ERROR: "/etc/lvmtab" doesn't exist; please run vgscan
+ /sbin/vgscan
vgscan -- LVM driver/module not loaded?
So my question is what should I do to verify the state of LVM on the
system?
Regards,
Gerry Reno
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox