All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Fralich" <sjfralic@syr.edu>
To: linux-lvm@sistina.com
Subject: [linux-lvm] pvmove error
Date: Mon Jul 14 13:25:02 2003	[thread overview]
Message-ID: <sf12bd11.080@gwia201.syr.edu> (raw)

I'm running RedHat 9.  pvmove works fine with the LVM and kernel that come with RH9.  I would like to use XFS in place of ext3 though, which means patching the kernel.  I'm using the vanilla kernel 2.4.21 and lvm 1.0.7 (tools and driver).  Everything goes fine until I use pvmove.  I haven't patched the kernel for XFS yet, so the LVM patch is the only change to the kernel.   I'm using an IBM ServeRAID-4H card with the ips driver v6.00.31.  Any suggestions?  Thanks.

[root@sauron root]# pvmove -vv /dev/sdb /dev/sdc
pvmove -- checking name of source physical volume "/dev/sdb"
pvmove -- locking logical volume manager
pvmove -- reading data of source physical volume from "/dev/sdb"
pvmove -- checking volume group existence
pvmove -- reading data of volume group "vg03" from lvmtab
pvmove -- checking volume group consistency of "vg03"
pvmove -- searching for source physical volume "/dev/sdb" in volume group "vg03"
pvmove -- building list of possible destination physical volumes
pvmove -- checking destination physical volume names in command line
pvmove -- checking volume group activity
pvmove -- moving physical extents in active volume group "vg03"
pvmove -- WARNING: if you lose power during the move you may need
        to restore your LVM metadata from backup!
pvmove -- do you want to continue? [y/n] y
pvmove -- starting to move extents away from physical volume "/dev/sdb"
pvmove -- checking for enough free physical extents in "vg03"
lv: /dev/vg03/lv03[1]  old_dev: 08:16  new_dev: 08:32  old_pe_sector: 33152  new_pe_sector: 33152
pvmove -- opening output physical volume "/dev/sdc"
pvmove -- llseeking input physical volume "/dev/sdb"
pvmove -- llseeking output physical volume "/dev/sdc"
pvmove -- /dev/sdb [PE 0 [lv03 [LE 0]] -> /dev/sdc [PE 0] [1/8677]
pvmove -- copying extent from /dev/sdb::/dev/vg03/lv03(0x0810):33152 to /dev/sdc(0x0820):33152 on disk
/dev/vg03/group::/dev/vg03/lv03: 0810 33152, 0820 33152
pvmove -- ERROR "Inappropriate ioctl for device" copying extent from "/dev/sdb"

pvmove -- ERROR "Inappropriate ioctl for device" moving physical extents

This appears on the console as well :: 
lvm -- lvm_chr_ioctl: unknown command 0x4004fe51

Stephen

---------------------------------------------------------------------
Computer & Information Technology Group            help@ecs.syr.edu
College of Engineering & Computer Science          Link 204, 443-4308
Syracuse University

             reply	other threads:[~2003-07-14 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 13:25 Stephen Fralich [this message]
2003-07-16 14:38 ` [linux-lvm] pvmove error Juan Pablo Giménez
  -- strict thread matches above, loose matches on Subject: below --
2003-07-16 14:48 Stephen Fralich
2003-07-16  9:53 Stephen Fralich
2003-07-16 14:38 ` Juan Pablo Giménez
2001-06-26 13:40 S. Michael Denton
2001-06-26 13:49 ` Heinz J. Mauelshagen
2001-06-26  2:08 S. Michael Denton
2001-06-26 10:14 ` Heinz J. Mauelshagen
2001-06-26 11:25   ` S. Michael Denton
2001-06-26 12:15     ` Heinz J. Mauelshagen
2001-06-26 13:05       ` S. Michael Denton

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=sf12bd11.080@gwia201.syr.edu \
    --to=sjfralic@syr.edu \
    --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 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.