All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie Atherton <stunnel@attglobal.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] highmem64G Breaks My LVM
Date: Sun, 31 May 2009 23:39:44 -0700	[thread overview]
Message-ID: <4A2377B0.4000707@attglobal.net> (raw)

I originally posted this on the LinuxQuestions forum:  
http://www.linuxquestions.org/questions/slackware-14/highmem64g-kills-lvm-728418/

I have a fairly vanilla Slack 12.2 system.  I recently upped my memory 
to 8GB, and so recompiled the kernel, making a single change.  HIGNMEM4G 
was changed to HIGHMEM64G.  On re-booting, I could see the extra memory, 
but, unfortunately, I lost all my LVM volumes.

After a few checks, I found that vgscan was failing:

root@The-Tardis:~# vgscan --mknodes --verbose
    Wiping cache of LVM-capable devices
    Wiping internal VG cache
  Reading all physical volumes.  This may take a while...
    Finding all volume groups
  /dev/sda1: Checksum error
    Finding all logical volumes

If I reboot back to the HIGHMEM4G kernel, then all works fine again:

root@The-Tardis:~# vgscan --mknodes --verbose
    Wiping cache of LVM-capable devices
    Wiping internal VG cache
  Reading all physical volumes.  This may take a while...
    Finding all volume groups
    Finding volume group "raid_vg"
  Found volume group "raid_vg" using metadata type lvm2
    Finding all logical volumes

All the LVM volumes reside on an LSI megaRAID card, detected as 
/dev/sda, which is dedicated to a single PVM.

Any ideas why changing the HIGHMEM kernel option would break LVM.

Cheers,
Eddie

             reply	other threads:[~2009-06-01  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01  6:39 Eddie Atherton [this message]
2009-06-04  1:11 ` [linux-lvm] highmem64G Breaks My LVM Eddie Atherton
2009-06-27 21:32   ` Eddie Atherton

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=4A2377B0.4000707@attglobal.net \
    --to=stunnel@attglobal.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.