All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rainer Fügenstein" <rfu@oudeis.org>
To: "Rainer Fügenstein" <rfu@oudeis.org>
Cc: Phil Turmel <philip@turmel.org>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re[3]: Found duplicate PV: using /dev/sda3 not /dev/md1
Date: Wed, 6 Aug 2014 14:49:39 +0200	[thread overview]
Message-ID: <434471753.20140806144939@oudeis.org> (raw)
In-Reply-To: <1769771799.20140617161255@oudeis.org>

Hi,

I assume we hit a dead end here?

RF> [root@gateway ~]# dmsetup ls
RF> vg_gateway-lv_data      (253, 2)
RF> vg_gateway-lv_var       (253, 1)
RF> vg_gateway-lv_home      (253, 0)
RF> [root@gateway ~]#

[...] (see my last mail regarding this topic)

I wonder what will happen if I mdadmin --resize /dev/md1? presumably
it will overwrite this stray LVM superblock and raid volume content
will be the same as it was a few weeks ago, when this problem first
occured?

tnx


      reply	other threads:[~2014-08-06 12:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 21:58 Found duplicate PV: using /dev/sda3 not /dev/md1 Rainer Fügenstein
2014-06-15 18:35 ` Rainer Fügenstein
2014-06-16  2:46   ` Phil Turmel
     [not found]     ` <19411862.20140616155327@oudeis.org>
2014-06-16 14:35       ` Phil Turmel
2014-06-16 18:20         ` Re[2]: " Rainer Fügenstein
2014-06-16 20:15           ` Phil Turmel
2014-06-16 20:28             ` Re[2]: " Rainer Fügenstein
2014-06-16 20:54               ` Phil Turmel
2014-06-17  1:27                 ` Re[2]: " Rainer Fügenstein
2014-06-17 11:57                   ` Phil Turmel
2014-06-17 12:00                     ` Phil Turmel
2014-06-17 14:12                     ` Re[2]: " Rainer Fügenstein
2014-08-06 12:49                       ` Rainer Fügenstein [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=434471753.20140806144939@oudeis.org \
    --to=rfu@oudeis.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.org \
    /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.