On Fri, Oct 14, 2011 at 3:00 PM, <[1][email protected]> wrote:
Unfortunately I could not understand well what you wrote.
I try explaining what whiteout is. If you still have a question about
it, then post again.
Thank you for your quick response. I am sorry that I wasn't clear.
When you remove /aufs/fileA, then /rw/.wh.fileA is created. /ro/fileA
doesn't change. You cannot see both of /aufs/fileA and /aufs/.wh.fileA.
In this case the whiteout ".wh.fileA" just hides the "fileA" on /ro only,
nothing else will be hidden.
Do you mean you don't want /aufs/.wh.fileA, but want to hide /rw/fileA?
Yes, I don't want /aufs/.wh.fileA. If the user removes the file /aufs/fileA
then I just want the file /rw/fileA to be deleted (which I assume happens)
and the original file /ro/fileA will show through.
If you remove /rw/.wh.fileA or /rw/fileA manually, then unchanged
/ro/fileA will appear again. But probably you will need
CONFIG_AUFS_HNOTIFY and the mount option "udba=notify".
In my application I cannot manually remove /rw/fileA. My preference is not
to make the whiteout file to start.
References
1. mailto:[email protected]
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
