Rene Meusel: > The inode number changed back, mapping file1 again to the original file res= > iding in the read-only branch. Is it somehow possible to find out all inode= > numbers associated with one file name in the aufs union volume? Because th= > ere has to be more than one inode number associated internally with file1. = > Otherwise it would not be possible to change it back to the original one af= > ter deleting the copied up file from the writable branch.
Still I don't understand what you want to do. You may be misunderstaing how aufs assigns the inode number. It is based upon the inode number on the branch fs, instead of filename. You may think "file1" has inumA or inumB. That is wrong. In your case, you have file1 and file3 on your branch fs. And of course your branch fs assigns the inode number for them individually. Let's call it inum1 and inum3 here. Aufs creates a map something like - inum1 on branchA is aufs's i12. - inum3 on branchA is aufs's i14. (these numbers are borrowed from your mail). Finally if you really want to know these mappings, just run "ls -i /aufs/fileA /branch/fileA" By the way, if you remove a file on the writable branch directly (bypassing aufs)), then you SHOULD specify udba=notify and it may affect the aufs's inode numbering. J. R. Okajima ------------------------------------------------------------------------------ FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev
