linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] vgdisplay - checksum error - what does it mean?
Date: Sat, 17 Feb 2007 13:56:44 +0100	[thread overview]
Message-ID: <20070217125644.GC11919@percy.comedia.it> (raw)
In-Reply-To: <45D57D16.8060902@wpkg.org>

On Fri, Feb 16, 2007 at 10:44:54AM +0100, Tomasz Chmielewski wrote:
>>>So this basically means, that LVM was set up on /dev/sda2 some time 
>>>ago, but it was never removed from there - instead, RAID-10 was set up 
>>>on that partition?
>>
>>I don't think so. if sda2 is part of a raid10 md array probably the
>>beginning sector of the md device maps to the beginning sector of the
>>real device, hence lvm will find an lvm signature on /dev/sda2.
>
>Is there a way to check if it's really the case?

dd?

>There's something wrong with /dev/sda2 - lvmdiskscan claims it's a 
>371.58 GB LVM physical volume, while /dev/md2 is the physical volume I use.
>
>   /dev/sda2                     [      371.58 GB] LVM physical volume
>   /dev/md2                      [      743.16 GB] LVM physical volume
>
>
>>>Should I do something to fix the things? What?
>>yes, re-enable md_component_detection in lvm.conf, why did you disable
>>that?
>
>Certainly I didn't touch anything in /etc/lvm/*.
>If I look into /etc/lvm/lvm.conf, it says:
>
>devices {
>(...)
>     # By default, LVM2 will ignore devices used as components of
>     # software RAID (md) devices by looking for md superblocks.
>     # 1 enables; 0 disables.
>     md_component_detection = 1
>}
>
>It's enabled.
>
>So the problem is somewhere else. Where?

with md_component_detection enabled lvm should ignore /dev/sda2.
can you send the output of lvmdiskscan -vvv?

>BTW, the machine is running Debian etch (ARM port).
mmm i don't have an arm maybe this is the issue why lvm does not
understand that sda2 is a md component?!?

>"smartctl" says all four disks are fine (they are quite new, too), so 
>it's definitely not a hardware problem.
sure it is not an hw problem do not worry.

>I guess one way to fix it would be mark all partitions faulty on 
>/dev/sda, and then, to recreate the RAIDs.
>But I'm curious to know how could I handle such a situation if I didn't 
>have RAID.
what would it fix? you have no problem except lvm2 believing sda2 is an
lvm volume which is not.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  reply	other threads:[~2007-02-17 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 11:50 [linux-lvm] vgdisplay - checksum error - what does it mean? Tomasz Chmielewski
2007-02-15 15:23 ` Tomasz Chmielewski
2007-02-16  7:47   ` Luca Berra
2007-02-16  9:44     ` Tomasz Chmielewski
2007-02-17 12:56       ` Luca Berra [this message]
2007-02-17 18:34         ` Alasdair G Kergon
2007-02-22 13:21           ` Tomasz Chmielewski
2007-02-22 13:55             ` Tomasz Chmielewski
2007-02-25  8:38               ` Luca Berra
2007-03-02 11:36                 ` Tomasz Chmielewski
2007-03-02 11:48                   ` Tomasz Chmielewski

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=20070217125644.GC11919@percy.comedia.it \
    --to=bluca@comedia.it \
    --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).