All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] LVM 0.9 vgscan problem
@ 2001-01-07  4:08 Brad Corsello
  2001-01-07 16:12 ` Jan Niehusmann
  0 siblings, 1 reply; 7+ messages in thread
From: Brad Corsello @ 2001-01-07  4:08 UTC (permalink / raw)
  To: linux-lvm

OK, Jan's patch fixed the vgextend problem on my machine, at least.  I
manually made the changes to the lvm.c that ships with 2.4.0 and recompiled
the module, and I succesfully did a few vgextend operations.  We're just
commenting out one line and adding two lines in a different place.  Jan's
patch does not appear to be against the version of lvm.c that ships with
2.4.0, so I didn't try to apply it.  A patch against the version of lvm.c that
ships with 2.4.0 follows (sorry if the format is wrong, I don't usually do
this sort of thing):

---------------

--- lvmbackup/lvm.c     Fri Jan  5 19:10:25 2001
+++ /usr/src/linux/drivers/md/lvm.c     Sat Jan  6 22:41:22 2001
@@ -2021,9 +2021,10 @@ static int lvm_do_vg_extend(vg_t *vg_ptr
                for (p = 0; p < vg_ptr->pv_max; p++) {
                        if ( ( pv_ptr = vg_ptr->pv[p]) == NULL) {
                                ret = lvm_do_pv_create(arg, vg_ptr, p);
-                               lvm_do_create_proc_entry_of_pv ( vg_ptr,
pv_ptr);
+/*                             lvm_do_create_proc_entry_of_pv ( vg_ptr,
pv_ptr); */
                                if ( ret != 0) return ret;
-       
+                               pv_ptr = vg_ptr->pv[p];
+                               lvm_do_create_proc_entry_of_pv ( vg_ptr,
pv_ptr);
                                /* We don't need the PE list
                                   in kernel space like LVs pe_t list */
                                pv_ptr->pe = NULL;

^ permalink raw reply	[flat|nested] 7+ messages in thread
* [linux-lvm] LVM 0.9 vgscan problem
@ 2001-01-03 22:56 Rik van Riel
  2001-01-04 17:49 ` Rik van Riel
  0 siblings, 1 reply; 7+ messages in thread
From: Rik van Riel @ 2001-01-03 22:56 UTC (permalink / raw)
  To: linux-lvm; +Cc: linux-kernel

Hi,

I have a strange problem (preventing me from testing the latest
2.4 kernel ... *sigh*) with my LVM setup.

The latest LVM utils + the latest kernel works just fine on my
test machine, but breaks horribly on my workstation. The only
difference I have found is that one PV of my VG has "NOT available"
as PV Status ...

--- Physical volume ---
PV Name               /dev/hda5
VG Name               vg0
PV Size               4.4 GB / NOT usable 2.56 MB [LVM: 124 KB]
PV#                   3
PV Status             NOT available
Allocatable           yes
Cur LV                0
PE Size (KByte)       4096
Total PE              1125
Free PE               1125
Allocated PE          0

Any chance of getting the LVM utilities fixed ?

I'd hate to see LVM be the showstopper for 2.4
(then again, the way the LVM team has neglected
everything from backwards compatability to even
documenting such is pretty much a showstopper in
itself ...)

regards,

Rik
--
Hollywood goes for world dumbination,
	Trailer at 11.

		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com.br/

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2001-01-07 16:12 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-01-07  4:08 [linux-lvm] LVM 0.9 vgscan problem Brad Corsello
2001-01-07 16:12 ` Jan Niehusmann
  -- strict thread matches above, loose matches on Subject: below --
2001-01-03 22:56 Rik van Riel
2001-01-04 17:49 ` Rik van Riel
2001-01-05  3:56   ` Paul Jakma
2001-01-05 15:29     ` Heinz J. Mauelshagen
2001-01-05 15:27       ` Paul Jakma

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.