From: Rickard Olsson <richie@webhackande.se>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] FYI: Going back to LVM1 from LVM2
Date: Thu Sep 18 08:09:02 2003 [thread overview]
Message-ID: <3F69AE57.7040405@webhackande.se> (raw)
In-Reply-To: <0F72BC18-E849-11D7-B784-000393DC1896@sistina.com>
AJ Lewis wrote:
> If device nodes are missing, vgmknodes should help in LVM1.
I didn't know that, but I had the opportunity to test it, as the
/dev/f2/f2 LV went missing again after a reboot. vgmknodes reported
success, but mount still did not find the node until after a vgchange
-an / vgchange -ay combo. Weird.
As I mentioned earlier, I did install and run LVM2 on this machine
before going back to LVM1 (even going back and forth a few times) and I
suppose it's possible that this changed something in the metadata that
LVM1 didn't like.
/ Rickard Olsson,IT-Konsult/
/ Telefon: +46 70 635 01 42/
/ http://www.webhackande.se/
next prev parent reply other threads:[~2003-09-18 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 6:49 [linux-lvm] Kernel oops Tracy R Reed
2003-09-16 4:50 ` [linux-lvm] FYI: Going back to LVM1 from LVM2 Rickard Olsson
2003-09-16 8:25 ` AJ Lewis
2003-09-18 8:09 ` Rickard Olsson [this message]
2003-09-16 13:19 ` [linux-lvm] Kernel oops Tracy R Reed
2003-09-23 23:14 ` [linux-lvm] remove Gene
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=3F69AE57.7040405@webhackande.se \
--to=richie@webhackande.se \
--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