Hello Ken, Ken Trumbo: > I have a read-write mount over top of a read only filesystem. I want users > to be able to create and delete their own files or overwrite existing files > but not whiteout any files from the read only filesystem and if a modified > file is deleted the read only version becomes visible again. Is such a > scenario possible with aufs? I can't seem to figure out a way.
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. The whiteout is a secret file to hide the file on the lower branch. Assume, - /aufs = /rw + /ro - /ro/fileA exists, but /rw/fileA. - so /aufs/fileA exists too. If you modify /aufs/fileA, then aufs will copies-up the file to /rw and then modify it. /ro/fileA is unchanged. Now you have /rw/fileA and /ro/fileA, but /ro/fileA is not visible through /aufs. 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? Do you want another whiteout implemented as xattr or something? 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". J. R. Okajima ------------------------------------------------------------------------------ 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
