Linux LVM users
 help / color / mirror / Atom feed
From: Per Kristiansen <per@gathering.org>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Changing Controller and also device names
Date: Wed Nov  6 07:27:01 2002	[thread overview]
Message-ID: <20021106142554.N30327@gathering.org> (raw)

Got a fun problem here.

I have a IDE controller that I have hooked up 7 disks to.

Now I've found that the controller is acting VERY strange, and want to exchange it with
another one.


Today I have:

PV Name (#)           /dev/hdk1 (5)
PV Status             available / allocatable
Total PE / Free PE    3680 / 0

PV Name (#)           /dev/hdl1 (7)
PV Status             available / allocatable
Total PE / Free PE    2980 / 0

PV Name (#)           /dev/hdi1 (1)
PV Status             available / allocatable
Total PE / Free PE    3680 / 0

PV Name (#)           /dev/hdj1 (2)
PV Status             available / allocatable
Total PE / Free PE    3680 / 0

PV Name (#)           /dev/hdg1 (4)
PV Status             available / allocatable
Total PE / Free PE    3576 / 0

PV Name (#)           /dev/hde1 (6)
PV Status             available / allocatable
Total PE / Free PE    3576 / 0

PV Name (#)           /dev/hdf1 (3)
PV Status             available / allocatable
Total PE / Free PE    3576 / 0


Do I need to take SPECIAL care to get the same device names  when I move the disks to the new controller
or can it find the data it needs using vgscan/pvscan ?

and no...
no raid or anything..it's not really a critical server as everything is backed up everyday.

-- 
Per Kristiansen
per@gathering.org

             reply	other threads:[~2002-11-06  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  7:27 Per Kristiansen [this message]
2002-11-06  7:40 ` [linux-lvm] Changing Controller and also device names Joe Thornber

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=20021106142554.N30327@gathering.org \
    --to=per@gathering.org \
    --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