From: Eric Brunson <brunson@brunson.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] re-activate lv after reboot ?
Date: Tue, 21 Apr 2009 10:15:38 -0600 [thread overview]
Message-ID: <49EDF12A.8@brunson.com> (raw)
In-Reply-To: <49EDEEA5.6060409@sivell.com>
On 04/21/2009 10:04 AM, vu pham wrote:
> Eric Brunson wrote:
>> On 04/21/2009 09:47 AM, vu pham wrote:
>>> My server uses iscsiadm to access a remote iscsi device. VG and LV
>>> are created on that device and can be accessed just fine.
>>> The problem is after reboot, the LVs are in inactive mode and I have
>>> to run vgchange -a y to activate the VG on the iscsi device or to
>>> put that command /etc/rcd./rc.local.
>>
>> In RH and Fedora you need to updated your initrd image to have the
>> drivers for the disk access available before the real filesystems are
>> mounted. You don't mention what distro you're using, so I'll avoid
>> boring you with details that may not be pertinent to your situation.
>>
>
> Hi Eric, thanks for your reply. I am using RHEL5.3
>
In Fedora (and I assume RH) you can specify additional kernel modules to
include in the initrd image:
foxtrot(~)$ cat /etc/sysconfig/mkinitrd
MODULES="usb-storage"
This will also "stick" across kernel upgrades as mkinitrd is part of the
kernel post-install process.
I don't know anything about iscsiadm, if it's simply a kernel module,
then you can add it as I added usb-storage, if it's a process that has
to be running, that may be more difficult to add to your boot process.
That's the extent of my expertise, so maybe someone familiar with
iscsiadm may chime in.
Hope that helps,
e.
next prev parent reply other threads:[~2009-04-21 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 15:47 [linux-lvm] re-activate lv after reboot ? vu pham
2009-04-21 15:58 ` Eric Brunson
2009-04-21 16:04 ` vu pham
2009-04-21 16:15 ` Eric Brunson [this message]
2009-04-23 3:46 ` Edward Choi
2009-04-23 11:23 ` Vu Pham
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=49EDF12A.8@brunson.com \
--to=brunson@brunson.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).