From: Brad Corsello <bcorsello@usa.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] LVM 0.9 vgscan problem
Date: Sat, 06 Jan 2001 23:08:03 -0500 [thread overview]
Message-ID: <04b311608040711NYCSMTP1@nyc.rr.com> (raw)
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;
next reply other threads:[~2001-01-07 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 4:08 Brad Corsello [this message]
2001-01-07 16:12 ` [linux-lvm] LVM 0.9 vgscan problem 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
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=04b311608040711NYCSMTP1@nyc.rr.com \
--to=bcorsello@usa.net \
--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