On Sun, Aug 17, 2003 at 01:46:38PM +0200, Jan Niehusmann wrote: > I hope this helps - do you have a suggestion on what to try next? This is the first clue: activate/dev_manager.c:487 pvmove Mirror status: 2 003:004 009:002 383/384 activate/dev_manager.c:532 pvmove Mirror percent: 99.739586 383/384 means the kernel mirror has only successfully copied 383 out of 384 512-KB regions from (major, minor) (3,4) to (9,2). The first pvmove segment has 12 16MB extents = 393216 sectors = 384 512KB regions. Can you check (e.g. using dd) all the old sectors can be read OK, and the new ones written to OK? (Though you're not seeing kernel error messages; but some volume moves work OK, so an off-by-one theory is unlikely or nothing would work?) The first entry of 'dmsetup table vgraid-pvmove0' would show you the sector ranges - 30448+3156 on pv1=/dev/hda4, length above & 384 on pv0=/dev/md2 ? [NB Be careful not to overwrite data - if you've done some other successful pvmoves since, some of those /dev/md2 sectors might now be allocated onto.] We haven't implemented bad sector error reporting and handling yet, so for now, you have to construct pvmoves to avoid any bad sectors. Alasdair _______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
