From: zoo1@corecomm.net
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] vgscan fails to find vg
Date: Sat, 17 Jun 2000 14:13:44 -0400 [thread overview]
Message-ID: <20000617141344.A2117@bar.nowhere> (raw)
In-Reply-To: <20000617175854.A7641@hmsysv.t-online.de>; from Mauelshagen@Sistina.com on Sat, Jun 17, 2000 at 05:58:54PM +0200
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Sat, Jun 17, 2000 at 05:58:54PM +0200, Heinz J. Mauelshagen wrote:
><SNIP vgscan utput>
>The output shows, that the Volume Group is exported.
yes; i'm sorry, this was a side effect of my working around the problem
with vgexport / vgimport.
i shut down without exporting the vg, only deactivating it, and
restarted again with the following commands in rc.sysinit:
/sbin/vgscan -v -d > /root/vgscan.1 2> /root/vgscan.2
/sbin/vgchange -v -d -a y > /root/vgchange.1 2> /root/vgchange.2
this failed to come up, so i then had to restart again with my usual
vgexport / import, but at least i think i've got good logfiles this
time. since they became longish, i've tarred and gzipped them and
attached the tarfile to this email; i hope the mailing list software
doesn't dislike mime attachments. :-/
[-- Attachment #2: vgoutput.tar.gz --]
[-- Type: application/octet-stream, Size: 10569 bytes --]
next prev parent reply other threads:[~2000-06-17 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-13 11:29 [linux-lvm] vgscan fails to find vg zoo1
2000-06-17 15:58 ` Heinz J. Mauelshagen
2000-06-17 18:13 ` zoo1 [this message]
2000-06-19 8:32 ` Heinz J. Mauelshagen
2000-06-19 21:57 ` zoo1
-- strict thread matches above, loose matches on Subject: below --
2000-06-19 20:43 Michael Marxmeier
2000-06-19 23:13 ` zoo1
2000-06-12 23:08 zoo1
2000-06-13 10:07 ` Heinz J. Mauelshagen
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=20000617141344.A2117@bar.nowhere \
--to=zoo1@corecomm.net \
--cc=linux-lvm@msede.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