Drunkard Zhang <gongfan193@xxxxxxxxx> writes: > 2010/7/22 Ted Ts'o <tytso@xxxxxxx>: >> On Thu, Jul 22, 2010 at 05:39:16PM +0800, Drunkard Zhang wrote: >>> I run into a oops when mirgate /vz directory to ext4 lvm under gentoo + openvz. >> >> What were you doing precisely at the time of the oops? The oops logs >> indicates it was a cp, but a cp of what? And is this somethign you >> can easily reproduce? >> Wow. Sorry almost missed that thread. 2.6.32-openvz-budarin.1 does not contains any specific patches for ext4. So it is probably memory corruption caused by ovz stuff (2.6.32 is still experimental), or you caught unknown bug, the later it very unlikely because "cp" is very popular cmd :) I'll try to reproduce your issue. > I did: "/etc/init.d/vz start" with vpsid 101 and 109, which from: > http://bb.xnull.de/projects/gentoo/amd64/stage4-amd64-current.tar.bz2 > following the guide from: > http://www.gentoo.org/proj/en/vps/openvz-howto.xml > > Didn't change the content of stage4-amd64-current.tar.bz2 yet. > It looks like when "/etc/init.d/vz start", it will cp all files from > /vz/private/101/ to /vz/root/root/101/ That's not true, root/$veid is just stacked filesystem on top of private/$veid. > > The oops allways reproduced yesterday between reboot and kernel > remake, but this morning when I trying to finger out the oops point > using strace, I can't get the oops anymore. Sorry for interrupt,:-( > > Maybe distcc caused problem? I used to make kernel... Sorry again. > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
