On Thu, 2 Dec 2010 11:57:22 +0100 Michael Leun <lkml20101129@xxxxxxxxxxxxxxx> wrote: > > Can you please describe in detail the workload that's causing this > > to happen? > > Thats rather complicated, but I'll try. Basically it boils down to: > > unshare -n -m /bin/bash > unionfs -o > cow,suid,allow_other,max_files=65536 /home/netenv/user1-union=RW:/=RO /home/netenv/user1 > mount -n -t proc none /home/netenv/user1/proc mount -n -t sysfs > none /home/netenv/user1/sys mount -n -t devtmpfs > devtmpfs /home/netenv/user1/dev mount -n -t devpts > devpts /home/netenv/user1/dev/pts chroot /home/netenv/user1 /bin/su - > user1 [...] > In some of this setups two or more environments share the same > writable branch, so the files in this environments changed against > real root of the machine are the same, e.g.: > > [...] > unionfs -o > cow,suid,allow_other,max_files=65536 /home/netenv/commondir=RW:/=RO /home/netenv/user1 > [...] > > and another one > > [...] > unionfs -o > cow,suid,allow_other,max_files=65536 /home/netenv/commondir=RW:/=RO /home/netenv/user2 > [...] Additional note: Happens also WITHOUT that "two unionfs mounts use the same branch dir" stuff. Really seems to happen much more often in 2.6.36.1 than in 2.6.36. > I observed that unionfs process takes much more cpu power than usual > before fault happens. This also happens without that "two unionfs mounts use the same branch dir" stuff. -- MfG, Michael Leun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>