From: Eugene Vilensky <evilensky@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] vg availability during boot
Date: Thu, 3 Sep 2009 08:27:18 -0500 [thread overview]
Message-ID: <f4f537b50909030627i9117a53lbef23eddeb3a87e6@mail.gmail.com> (raw)
Greetings,
I have a host that refuses to recognize my san-attached logical
volumes during boot. When mounting from /etc/fstab, it drops out of
boot complaining that the LVs in question have an invalid superblock
and need to be fsck-ed, however because the lv is "mounted" the fsck
cannot proceed.
I commented out the entries, rebooted, and noticed that the LVs in the
VG in question are "NOT AVAILABLE." A vgchange -a y vgname later and
everything is working perfectly.
This is my first RHEL5 san-attached host; might I have missed some
sort of 'vg persistency' settings by doing the same things I've been
doing on RHEL4?
Thanks,
next reply other threads:[~2009-09-03 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 13:27 Eugene Vilensky [this message]
2009-09-04 14:07 ` [linux-lvm] vg availability during boot Larsen, Peter
2009-09-06 16:21 ` Eugene Vilensky
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=f4f537b50909030627i9117a53lbef23eddeb3a87e6@mail.gmail.com \
--to=evilensky@gmail.com \
--cc=linux-lvm@redhat.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).