All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ralf Müller" <ralf@bj-ig.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Problem with pvmove of system installation volume
Date: Thu, 2 Dec 2004 18:47:55 +0100	[thread overview]
Message-ID: <200412021848.01813@bj-ig.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 3966 bytes --]

Hi there,

the day before I started to do my first tests with lvm on Linux. I 
installed a fresh SuSE 9.2 on a machine with two identical disks, 
created 3 RAID 1 partitions and created on top of all this my first 
logical volume on Linux. Actually I created this "root" volume first, 
and installed SuSE on it. No problems so far. I was able to increase 
the "root" volume, I was able to create another "test" volume and 
shrink it when it was not mounted ... cool stuff - really.

The next thing I wanted to test was moving a logical volume from one 
physical volume to another. Usecase: replacement of an old/too 
small/for whatever reason unwanted disk by another. This was perfectly 
ok with the "test" volume - the one that I was able to shrink before. 
But when I tried the same with the "root" volume pvmove locked and I 
had to reset the machine. On the next boot the machine reported 
problems with the volume group on which the root volume is located and 
entered a recovery shell. There I had to call "lvm pvmove --abort" and 
after another restart the machine booted again. After this first 
experience I tried to upgrade the pached SuSE 2.6.8 kernel to a vanilla 
2.6.9 from kernel.org, I upgraded the lvm2 binaries from version 2.0.25 
to 2.0.29 - no changes. I googled around ... I found some reports about 
problems with pvmove - but nothing that matched my actual problem (as 
far as I can see it). So my hope is that someone here can help me a 
step further with this problem.

There were no messages in syslog when the machine stopped. The visible 
output of "pvmove -vv -n Root /dev/md0 /dev/md2" was:
      Setting global/locking_type to 1
      Setting global/locking_dir to /var/lock/lvm
      File-based locking enabled.
      /dev/md0: lvm2 label detected
      /dev/md0: lvm2 label detected
      /dev/md0: lvm2 label detected
      /dev/md1: lvm2 label detected
      /dev/md2: lvm2 label detected
      /dev/hda3: No label detected
      /dev/hdc3: No label detected
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
    Finding volume group "system"
      Locking /var/lock/lvm/V_system WB
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
    Archiving volume group "system" metadata.
    Creating logical volume pvmove0
      Getting target version for mirror
      Moving /dev/md0:0-1023 of system/Root
      Moving /dev/md0:1610-1737 of system/Root
    Moving 1152 extents of logical volume system/Root
      Finding volume group for uuid 
Qo3GHB44Twwv7MYsUjJtWUCuPH5P2vviIikXQlamoffNvHYy5DUCF66jqwCCepYC
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
    Found volume group "system"
      Setting activation/missing_stripe_filler to /dev/ioerror
    Updating volume group metadata
    Creating volume group backup "/etc/lvm/backup/system"
      Finding volume group for uuid 
Qo3GHB44Twwv7MYsUjJtWUCuPH5P2vviIikXQlamoffNvHYy5DUCF66jqwCCepYC
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
    Found volume group "system"
      Locking memory
      Suspending system-Root
      Finding volume group for uuid 
Qo3GHB44Twwv7MYsUjJtWUCuPH5P2vviK1M7zT9n1b350JWv5oYIL2CJuiUVy1iz
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
      /dev/md0: lvm2 label detected
      /dev/md2: lvm2 label detected
    Found volume group "system"
    Loading system-pvmove0
      Setting activation/mirror_region_size to 512

-- 
Van Roy's Law: -------------------------------------------------------
       An unbreakable toy is useful for breaking other toys.

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-12-02 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 17:47 Ralf Müller [this message]
2004-12-03 11:05 ` [linux-lvm] Problem with pvmove of system installation volume Ralf Müller

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=200412021848.01813@bj-ig.de \
    --to=ralf@bj-ig.de \
    --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 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.