"Jrgen_P._Tjern": > Yes, but the kernel / userspace is 32bit:
Ok, thank you. > * NFS server is turned on > * NFS-root client is turned on > - Everything works fine > * NFS server is rebooted, NFS-root client is not rebooted > * NFS server gets a *lot* of BUGs in dmesg I see. Such situation is beyond my expectations or imaginations. :-) I guess the root cause is related to the inode number in aufs. Basically, aufs stores its inode numbers to the xino files, and the xino files are volatile which means the xino files are totally gone after the aufs is unmounted. Mounting aufs again with the same branches, the new aufs will have new, different set of inode numbers. When the nfs client accesses to nfs server by oboleted inode number, aufs detects their inconsistency and call BUG_ON macro. I guess this is the story of your case. If it is true, the the quiestion is: does aufs needs persistent xino files? Junjiro Okajima ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
