Ken Trumbo:
> Yes, I know it sounds a bit strange at first.  For example, the user can
> modify a file and test the change (say to a file in /etc) and if they don't
> like the change deleting just reverts back to the previous version.

Generally I'd suggest to detach /rw from aufs for such case.


> I can investigate FUSE but I think aufs is very close to what I need.  I am
> wondering if it is easy to patch aufs to not create the whiteout file.  Or,
> can I put the whiteout file into some 'nullfs'.

It is easy to stop creating whiteout.
If you really want, then take a look at fs/aufs/i_op_del.c.
- au_wr_dir_need_wh() decides whether a new whiteout is necessary or
  not.
- lock_hdir_create_wh() calls fs/aufs/whout.c:au_wh_create() to create
  the whiteout.
Of course fs/aufs/i_op_del.c:aufs_unlink() is the body of unlink(2).


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

Reply via email to