-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: > Jorgen, > Thank you for sending logs. > Let's change the thread and continue the discussion a little more. > > I think that make the xino files to be persistent is most hopeful, but > it may be difficult to ensure the branch set is perfectly the same. > > With the persistent xino files will allow you to: > # mount -t aufs -o br:<branch set A>,keep_xino none /aufs > # umount /aufs and keep the xino files > # mount -t aufs -o br:<branch set A>,use_old_xino none /aufs > > But if you give different branch set to the second aufs mounting, you > may be totally lose since it is hard to judge the correctness of > matching xino files and the branch set. > The uuid on a filesystem may be helpful, but the recent vmware/xen users > may not pay attentions to uuid. If the uuid is illegally set to the > branch fs, it must be useless. Well, I'm not too good at this, but my suggestion is to have an option (compiletime or runtime) to separate to one xino-file per underlying FS (indexed by UUID), and to be able to specify what dir to write (or read - - using your suggested keep_xino-option) them from. Example: # mount -t aufs -o br:<branch set A>,keep_xino,xino=/tmp/.aufs.xino.dir/ /aufs # umount /aufs keeping the xino files # mount -t aufs -o br:<perhaps not branch set A>,keep_xino,xino=/tmp/.aufs.xino.dir/ /aufs
When I mount again, it will find files in /tmp/.aufs.xino.dir/ that matche the uuid of the members of the branch set specified, and use those as a base (but creating new xino-files for uuids that are not in /tmp/.aufs.xino.dir/). Does that make sense? Would it be doable? > About the approach you wrote which is to make nfs client to re-lookup > the inodes after rebooting, I am afraid it means nfs server will return > ESTALE for almost all accesses, and the nfs-root client will not work > anymore. Ah, darn. This might though be a better "default behaviour" than kernel BUG on nfs server? Or is there another "temporary fix" that atleast won't make the aufs BUG when this happen? Kindest regards, Jørgen P. Tjernø -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+g2uUMzc1WGo4zgRAgHSAJ43YCMHDJBRHAUyw8CDtyxngk6XlwCfeTeq NDrU7uDnh18JkPrmxNKaVCE= =yljS -----END PGP SIGNATURE----- ------------------------------------------------------------------------- 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/
