From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgscan won't recognize my VG
Date: Fri, 23 Mar 2001 15:36:05 -0700 (MST) [thread overview]
Message-ID: <200103232236.f2NMa5h24294@webber.adilger.int> (raw)
In-Reply-To: <3ABB63F7.F776CCEA@in.tum.de> from David Vidal Rodriguez at "Mar 23, 2001 03:55:52 pm"
You write:
> > You don't need the beta6 kernel patch to run vgcfgrestore to restore UUIDs,
> > only the beta6 user tools.
>
> OK, but see what appears if I try to restore the VGDA... (the messages aren't
> exact)
>
> # vgcfgrestore -n <vg_name> -f <vgda_backup> <path_to_pv>
> Error "parameter error" while trying to restore
Bug in the code. Exact error would help.
> # cp <vgda_backup> /etc/lvmtab.d/<vg_name>
> # vgcfgrestore -n <vg_name> <path_to_pv>
> vgcfgrestore -- VGDA of vg <vg_name> successfully restored in <path_to_pv>
>
> # pvdata -U <path_to_pv>
> List of UUIDs:
> uuid0: <uuid1>
> uuid1: <uuid2>
> uuid2: --EMPTY--
It _should_ work, but why it doesn't, I don't know. Can you try running
"vgcfgrestore -v -d -n <vg_name> <path_to_pv>" and send the output
(compressed probably).
If possible, apply the following patch first, so we can be sure that it is
doing the right thing.
Cheers, Andreas
=========================================================================
diff -u -u -r1.1.2.2 pv_write_uuidlist.c
--- tools/lib/pv_write_uuidlist.c 2001/02/19 10:04:34 1.1.2.2
+++ tools/lib/pv_write_uuidlist.c 2001/03/23 22:27:15
@@ -45,7 +45,7 @@
int size = 0;
char *pv_uuid_list = NULL;
- debug_enter ( "pv_write_uuidlist -- CALLED\n");
+ debug_enter ( "pv_write_uuidlist -- CALLED for %s\n", pv_name);
if ( pv_name == NULL || pv_check_name ( pv_name) < 0 ||
vg == NULL || vg_check_name ( vg->vg_name) < 0) ret = -LVM_EPARAM;
@@ -77,6 +79,8 @@
memcpy(u, pv->pv_uuid, UUID_LEN);
u += NAME_LEN;
}
+ debug( "pv_write_uuidlist -- writing %d UUIDs on %s\n",
+ ( u - pv_uuid_list) / NAME_LEN, pv_name);
if ( write ( pv_handle, pv_uuid_list, size) != size)
ret = -LVM_EPV_WRITE_UUIDLIST_WRITE;
free ( pv_uuid_list);
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-23 22:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 20:13 [linux-lvm] vgscan won't recognize my VG David Vidal Rodriguez
2001-03-19 20:37 ` Andreas Dilger
2001-03-20 18:52 ` David Vidal Rodriguez
2001-03-20 19:17 ` AJ Lewis
2001-03-20 19:25 ` Andreas Dilger
2001-03-20 19:35 ` David Vidal Rodriguez
2001-03-20 20:00 ` David Vidal Rodriguez
2001-03-20 20:21 ` Andreas Dilger
2001-03-20 20:36 ` David Vidal Rodriguez
2001-03-21 0:29 ` Kirth
2001-03-21 18:30 ` David Vidal Rodriguez
2001-03-21 19:17 ` Andreas Dilger
2001-03-23 14:55 ` David Vidal Rodriguez
2001-03-23 22:36 ` Andreas Dilger [this message]
2001-03-20 20:57 ` [linux-lvm] LVM and fault tolerance Anders Widman
2001-03-21 17:33 ` Lars Kellogg-Stedman
2001-03-22 23:59 ` Anders Widman
[not found] ` <0103262137020G.01456@lyta>
2001-03-27 21:48 ` Anders Widman
2001-03-27 21:56 ` Ragnar Kjørstad
2001-03-27 22:29 ` Anders Widman
2001-03-27 22:45 ` Ragnar Kjørstad
2001-03-28 6:43 ` Russell Coker
2001-03-31 17:17 ` Anders Widman
2001-03-20 20:23 ` [linux-lvm] vgscan won't recognize my VG José Luis Domingo López
2001-03-20 19:31 ` AJ Lewis
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=200103232236.f2NMa5h24294@webber.adilger.int \
--to=adilger@turbolinux.com \
--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;
as well as URLs for NNTP newsgroup(s).