linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Strange messages on my Fedora Box
Date: Wed, 25 Jul 2007 18:37:13 +0200	[thread overview]
Message-ID: <46A77C39.90000@redhat.com> (raw)
In-Reply-To: <46A775F6.6000307@free.fr>


Georges Giralt wrote:
> Hi !
> The context :
> Fedora Core 7 on an X86-64  AMD Athlon 64x2 box.
> lvm> version
>    LVM version:     2.02.24 (2007-03-19)
>    Library version: 1.02.17 (2007-01-29)
>    Driver version:  4.11.0
> lvm>
> Kernel : 2.6.22.1-27.fc7
> 3 X 160 Gb disks with 4 primary partitions
> the 3 last partitions in each disks make 3 VG : vgF32, vgF64 and vg-Ext.
> I use LVM mirroring.

Mirror staus string is broken in 2.6.22 stable kernel, I hope that fix will be
part of next stable update.

patch exist for some time here
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-raid1-fix-status.patch


> The vgF32 vg hold a FC7 32 bits version, vgF64 the FC7 64 bits version 
> (the one I use now) and vg-Ext the home and various data.
> Today, i ran lvs and get the following message.
> I've nothing in the system message file nor in the dmesg ring.
> /bott is an md made with the 2 first partitions of the 2 first disks and 
> is fine.
> Questions :
> Is it serious ? What should I do ? How to recover ?

If you boot to 2.6.21 kernel, it should work ok, 2.6.23-rc1 has this fix too.
It is only reporting problem for mirrored volumes (in this case).
(But it is breaking pvmove functionallity too.)

Milan
--
mbroz@redhat.com

  reply	other threads:[~2007-07-25 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 16:10 [linux-lvm] Strange messages on my Fedora Box Georges Giralt
2007-07-25 16:37 ` Milan Broz [this message]
2007-07-25 16:55   ` Georges Giralt

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=46A77C39.90000@redhat.com \
    --to=mbroz@redhat.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).