Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] bug: raid1 sub-devices are scanned too
Date: Mon Feb 25 03:52:02 2002	[thread overview]
Message-ID: <20020225105242.B7948@sistina.com> (raw)
In-Reply-To: <20020224221642.GA31890@xulfad.ton.tut.fi>; from flux-lvm@inside.org on Mon, Feb 25, 2002 at 12:16:43AM +0200

On Mon, Feb 25, 2002 at 12:16:43AM +0200, Erkki Seppala wrote:
> Hello, thanks for the reply. 
> 
> The problem seems to have disappeared after a reboot, or then I've
> tried the vgscan -f -stuff - vgscan now just seemed to work OK. I
> could've sworn I tried that vgscan -f before without too much success,
> but, all in all, I imagine it's not worth hunting a bug before one can
> find an easily repeatible situation.

Yes, that's true.

In case you get it reproducable some day, I'ld really appreciate your
VGDA and setup information to drill that one down.

Regards,
Heinz    -- The LVM Guy --

> 
> On Sat, Feb 23, 2002 at 11:55:29AM +0100, Heinz J . Mauelshagen wrote:
> 
> > > this is a bug in 1.0.3 with exported VGs.
> > > 
> > > If you import your VG "mirror" again, you should be fine.
> > > Rather than imprting, "vgscan -f" should work as well.
> 
> In the original situation vgscan -f was of no help, only the
> export/import-trick (and a reboot) allowed me to access the mirror-vg.
> 
> > Are /dev/ide/host0/bus1/target1/lun0/part1 and
> > /dev/ide/host0/bus0/target1/lun0/part1 really the ones making up /dev/md/1 ?
> > 
> > Regards,
> > Heinz    -- The LVM Guy --
> 
> Yes:
> md1 : active raid1 ide/host0/bus1/target1/lun0/part1[1] ide/host0/bus0/target1/lun0/part1[0]
>       58633216 blocks [2/2] [UU]
> 
> -- 
>   _____________________________________________________________________
>      / __// /__ ____  __                              Erkki Seppälä\   \
>     / /_ / // // /\ \/ //ircnet                           Modeemi Ry\  /
>    /_/  /_/ \___/ /_/\_\@modeemi.fi        http://www.modeemi.fi/~flux/
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2002-02-25  3:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 19:55 [linux-lvm] bug: raid1 sub-devices are scanned too Erkki Seppala
2002-02-23  4:47 ` Heinz J . Mauelshagen
2002-02-23  4:55   ` Heinz J . Mauelshagen
2002-02-24 16:17     ` Erkki Seppala
2002-02-25  3:52       ` Heinz J . Mauelshagen [this message]

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=20020225105242.B7948@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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