linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jesse Molina <jesse@opendreams.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Can't use LVM1 VG/LVs under LVM2; LV xxx: inconsistent LE count 32 != 64
Date: Tue, 08 May 2007 21:54:53 -0700	[thread overview]
Message-ID: <4641541D.2010709@opendreams.net> (raw)


I'm having a problem getting a Debian system from Linux kernel 2.4 to 
2.6 due to LVM.  On the 2.4 kernel/LVM1, the VGs and LVs work fine, 
mount up, and show absolutely no sign of any problem.  However, I can't 
get the 2.6 kernel/LVM2 to activate the VGs at all.

I've filed a Debian bug, which has additional information, here;
	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422963



The interesting error messages under 2.6 include;

	"LV tmp: inconsistent LE count 32 != 64"
	
	"System ID sorrows1107837513 on /dev/sdd3 differs from 
sorrows1107837515 for volume group"

Notice how the LE count is about half of what it should be (reports 32, 
but is actually 64).  These LVs are striped across the two disks, thus 
two 32 LE stripes in each PV that make up the VG upon which this LV exists.

Bad error checking, or actual problem?  I don't know.



This person seems to have had the same problem, though he had four stripes;
	http://www.redhat.com/archives/linux-lvm/2006-October/msg00109.html

I originally reported this problem roughly eight months ago, with no 
resolution or response;
	http://www.redhat.com/archives/linux-lvm/2006-September/msg00010.html



Help?



-- 
# Jesse Molina
# Mail = jesse@opendreams.net
# Page = page-jesse@opendreams.net
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/

             reply	other threads:[~2007-05-09  4:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  4:54 Jesse Molina [this message]
2007-05-09  7:14 ` [linux-lvm] Can't use LVM1 VG/LVs under LVM2; LV xxx: inconsistent LE count 32 != 64 David Robinson
2007-05-09  9:40 ` Bryn M. Reeves
2007-05-09 18:28   ` Jesse Molina
2007-05-10  0:25     ` Jesse Molina

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=4641541D.2010709@opendreams.net \
    --to=jesse@opendreams.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 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).