A Dimarts, 11 de maig de 2010 17:29:42, vàreu escriure: > Then let me make sure what "previous releases of aufs" means. > You say your kernel is 2.6.33-3.slh.9-sidux-amd64. > What is your aufs version actually? You may say it is 2010-05-09, but > there is no such version of aufs. > Do you mean that > 2.6.33-3.slh.9-sidux-amd64 + aufs2-33-20100503 had no problem, but > 2.6.33-3.slh.9-sidux-amd64 + aufs2-33-20100510 doesn't work, right? > from the changelog of that package, I see that aufs2 was not changed from date: Mon, 26 Apr 2010, version 2.6.33-3.slh.1-sidux-amd64. * update aufs2 to 2010-04-26.
until 2010-05-09 2.6.33-3.slh.9-sidux-amd64. that is a listing of the patches that have been added to the latest sidux kernel, differences 2.6.33-3.slh.9(fails) from 2.6.33-3.slh.7(works) linux-sidux-2.6 (2.6.33-46) unstable; urgency=low * import 2.6.33.4-rc1. * update aufs2 to 2010-05-09. therefore I say that the problem comes from aufs because is not possible to modify a file on the aufs filesystem or edit it using vi , but we can do it successfully on another filesystem. > If you can use Magic SysRq Key, then try Alt+SysRq+a, d, w and t, and > please send me the output. If the process "mount -n -o move /lnet > /root/lnet" really stops, then the problem MAY exist it VFS, instead of > aufs I am afraid. Sorry, I have not explained correctly, the mount process not stops, the boot script is stopped at a breakpoint (set by an option cheatcode). I should remark that the incorrect behaviour is that the modification of files on the aufs filesystem is not successful until the main system init procedure is completed, and the full Linux OS has started. no info comes from that keys, kew w shows a line with empty info: Show Blocked State: key t also: Show State: the other keys, a and d are not defined on the SysRq Help menu, Jordi Pujol Live never ending Tale GNU/Linux Live forever! http://livenet.selfip.com ------------------------------------------------------------------------------
