A Dimecres 18 Maig 2011 10:42:53, Miklos Szeredi va escriure: > Documentation/filesystems/directory-locking > > for all the gory details. ok, i'll look this, > So, is there a minimal test case that I can try to replicate the bad > behavior? it's an occasional error, occurs when the system is occupied processing diverse tasks at the same time, for example when startpar is running in parallel the initialization of system daemons, this is detected because some changes done by the same daemon program are lost, (the case of consecutive sed instructions) or when doing a big upgrade of the system packages, some files are lost. I believe than this could be reproduced in an stress test, running a process that creates a lot of files around, deletes them and moves from tmpfs to overlays; and the system must be very busy, because this one and the others processeses are working hard. Thanks, Jordi Pujol Live never ending Tale GNU/Linux Live forever! http://livenet.selfip.com -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
