On Sat, Aug 16, 2003 at 07:56:06PM +0100, Alasdair G Kergon wrote: > If pvmove process itself freezes, then a long/wide 'ps' output for that > process, kcopyd & kmirrord (incl cols: NI, VSZ, RSS, STAT > and symbolic WCHAN). I noticed the WCHAN fields in my ps output were not very useful, because they pointed to a module and were not decoded. So I took the numeric value (92fa83) and looked it up by hand. It seems to point to the schedule() call in line 56 of dm-daemon.c for both kcopyd and kmirrord. And then, I made a quite worrying observation: When the hanging happens, the device being copied is in a completely garbled state. In this case, /dev/vgraid/lvol5 didn't look like an ext3 filesystem at all. So I looked at the underlying devices, and both /dev/hda4 and /dev/md2 had a copy of the actual filesystem, only differing in the last 512K. This conforms to the fact that the mirroring was done for all but one 512K block. But these 512K are completely different (target device all zeroes). However, these are only the underlying devices. Looking at /dev/vgraid/lvol5 a little bit closer revealed that it contained parts of some other filesystem. Very strange. And worrying. I don't even want to know if writing to this LV would overwrite some unrelated partition. Jan _______________________________________________ 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/
