> You don't get the problem here. 
  --- Probably :)

My experience is only of situations where there might be 4 duplicate files in 
different aufs branches, so I find all 4, then review the aufs mount sequence 
and finally review the aufs r/w branch  (in case it has been updated 
unexpectedly).

so if /mnt/aufs has
aufsbranch1
aufsbranch2
realdirectory1
realdirectory2

This is an issue with your implementation, as I suspect many keep the aufs 
branches in their own path (/mnt/aufs without real directories)

What I might understand is that xorg.conf is a file I want to find, and it 
exists 12 times in 96 branches of over 640,000 files yet there are only 4 
exact filenames with the complete path of /etc/X11/xorg.conf that create a 
conflict I need to resolve.

So the "useful tool" must identify
- aufs branch
- aufs load sequence
- file path
- file name

It takes 4 seconds on my system to issue this find command
find /mnt/aufs -name 'xorg.conf' | grep '/etc/X11/xorg.conf'

Note I do NOT search the / root path where a file will exist both in the aufs 
root overlay and the /mnt/aufs branches .. that would take hours!

What did I miss in understanding the problem and the frequency of it's 
challenge?

On Thursday 04 December 2008 08:38:16 am Kernel John wrote:
> 2008/11/25 Chuck Smith <[EMAIL PROTECTED]>
>
> > I have 96 mounted aufs squashfs modules having more than 640,000 files,
> > and I
> > find files searching this location using this method ... it is not time
> > intensive at all as it is in memory.
>
> You don't get the problem here. I don't want to search /mnt/aufs. I want to
> search all modules for a file which is placed (by aufs) in /mnt/aufs.
>
> Best,
> John




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Reply via email to