[linux-lvm] Problem with pvmove (LVM 1.0.4 Kernel 2.4.18)

Poul Petersen petersp at roguewave.com
Tue May 7 19:57:01 UTC 2002

	I have a dual P-II 400 running RedHat 7.2 and the 2.4.18 kernel.
I've installed LVM-1.0.4 from source  and I have two version of the 2.4.18
kernel installed:

	1) Stock 2.4.18 kernel
	2) 2.4.18 with the LVM 1.0.4 PATCHES/Makefile generated patch

	What I've been doing is creating a simple volume group with two
disks and creating a small logical volume, small enough that all PEs are
allocated in the first PV. I then issue a pvmove to move all the PEs to the
second PV. If I boot into kernel #1 from above, everyhing works fine. If I
use kernel #2, the pvmove hangs while moving the second PE (I'm using pvmove
-v, so I can see each PE as it is moved). Notice that I am trying to move
the PEs without even creating a filesystem in the LV, so there is not an
issue with the LV being mounted. I've tried strace'ing the process, but
there is no activity. It would seem that applying the Makefile generated
patch is the *right* thing to do, but it is breaking pvmove...

	Now, using the first kernel, I create an ext2 partition in the LV,
mount it and export it via NFS and start some activity from a client using
dd. I can then pvmove the PEs back and forth between the disks without any
problems. If however, I use an ext3 filesystem, I get the following:

kernel: journal_bmap_Rsmp_785a3b98: journal block not found at offset 268 on
kernel: Aborting journal on device lvm(58,0).
kernel: ext3_abort called.
kernel: EXT3-fs abort (device lvm(58,0)): ext3_journal_start: Detected
aborted journal
kernel: Remounting filesystem read-only
kernel: EXT3-fs error (device lvm(58,0)) in start_transaction: Journal has

	So, what am I missing here and what can I try next?



More information about the linux-lvm mailing list