On Mon, 2011-11-21 at 09:18 +0900, sf...@users.sourceforge.net wrote: > Hello tovis, > > "tovis": > > I have read man, aufs html documentation but I have still do not > > understand how to construct the command for making ro /var to be a unified > > with /tmp/var wr so in result every files in /var are seen by system but > > writes to /var goes to ramdisk/tmpfs ... > > Generally you can do it by > # mount -t aufs -o br:/tmp/var:/var none /var > > > > Should I make a separate ram disk (different from /tmp which is tmpfs)? > > What the correct syntax for this branch(?). Can I put it to fstab? Should > > I built a new initrd? > > - you can use any dir as an aufs branch (as long as it doesn't make a > loop with another branch). So you don't have to make a separate > ramdisk. > - you can write an aufs entry in your fstab if you want > - for initrd, it is totally up to > + what your initrd does > + what you want to do > + when your /var is mounted > + etc. > but generally, if you want to use aufs for /var only, then the above > command should be enough. > > I'd suggest you to check the aufs version in your debian system, since > it is known that aufs in debian is obsolete.
I should note that aufs is included in the Debian kernel only to support
the Debian Live system. So far as I know, it does work well enough for
that.
Debian unstable generally has the current version of aufs (old versions
usually won't compile due to VFS changes).
> Also aufs doesn't support linux-2.6.32 anymore. If you want to use aufs
> on linux-2.6.32, then I'd suggest you to get the last version of
> aufs2.1-32.
If there are important bug fixes that aren't in Debian 6.0 (squeeze)
then please inform debian-l...@lists.debian.org,
debian-ker...@lists.debian.org. The current version in squeeze is based
on:
commit a7f3024fe756f2ad59af8520e573c79220a73839
Author: J. R. Okajima <hooano...@yahoo.co.jp>
Date: Sun Jan 24 01:16:45 2010 +0900
aufs2 standalone version for linux-2.6.32
with the following fixes cherry-picked from aufs2-2.6:
commit e62ca9737674cf9b70a961cb8d1efed4a7cff976
Author: J. R. Okajima <hooano...@yahoo.co.jp>
Date: Mon Mar 1 17:52:50 2010 +0900
Revert "aufs: narrow down the BKL region"
commit 639e607997502dfe7dbe140c8de5d81ba99d4240
Author: J. R. Okajima <hooano...@yahoo.co.jp>
Date: Mon Mar 1 23:13:34 2010 +0900
Revert "aufs: bugfix, unlock mmap_sem temporary using BKL"
commit d986fa5a8557f6861fcac4106b6d75301bf5d118
Author: J. R. Okajima <hooano...@yahoo.co.jp>
Date: Mon Mar 8 23:45:56 2010 +0900
aufs: bugfix, another approach to keep the lock order of mmap_sem
commit b0372e021a903e33f39dd515ceebd8506b1c52aa
Author: J. R. Okajima <hooano...@yahoo.co.jp>
Date: Tue Jun 29 14:32:26 2010 +0900
aufs: bugfix, separate the workqueue for preprocessing mmap
> Note again, aufs2.1 is not maintained now.
Fair enough.
Ben.
--
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
