linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "roderick tapang" <retapang@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] rhel4 u4 lvm2 changes
Date: Fri, 24 Nov 2006 10:04:26 +0800	[thread overview]
Message-ID: <be7468bb0611231804t52eae9fejca8888109001c098@mail.gmail.com> (raw)

hi,

i installed RHEL4 update 4 (2.6.9-42.ELsmp) on an HP BL45p (AMD64). i
then added 4 EMC hosted disks on it:

/dev/emcpowerb    lx0060data00vg lvm2 a-   50.00G 24.00G
  /dev/emcpowerc    lx0060data00vg lvm2 a-   50.00G 24.00G
  /dev/emcpowerd    lx0060data00vg lvm2 a-   50.00G 24.00G
  /dev/emcpowere    lx0060data00vg lvm2 a-   50.00G 24.00G

i've create a couple of ext3 FS on this VG (LV striped across the
disks). everytime  i restart the system, i end up with the file system
repair prompt - the tw FS can't be mounted as the
PVs can't be seen.
i removed the entries in /etc/fstab. it appears that the PVs are not
being activated automatically during reboot. i had to do a:

lvmdiskcan
vgchange lx0060data00vg -ay

only then i can mount the FS.

/dev/mapper/lx0060data00vg-lx0060lvdata00   99G   92M   94G   1% /staging
/dev/mapper/lx0060data00vg-lx0060lvdata01  4.0G  1.9G  1.9G  51% /apps


 i have 6 other similar blade systems with  EMC disks allocated the
same way and they are all running RHEL4 update 3. but i never had this
kind of issue. are there any changes in the LVM2 activation during
bootup in update4?
i didn't find anything related to this in the release notes of update4
so i was hoping that someone could enlighten me on this. :)

many thanks.

erik
-- 
roderick e. tapang, nclp
retapang at gmail dot com

(o_.'       http://counter.li.org/
//\         ----------------------
V_/_        Linux User   #  253842

                 reply	other threads:[~2006-11-24  2:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=be7468bb0611231804t52eae9fejca8888109001c098@mail.gmail.com \
    --to=retapang@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).