Hi,
Tomas M:
> May I ask you, what is the trunc_xino useful for?
>
> I didn't find anything in aufs.5 documentation,
> only trunc_xib and notrunc_xib, but that is perhaps
> something else, am I right?
Right.
Because I don't know whether this feature is required or not, I didn't
write the documentation and marked it as experimental.
Hopefully these mail are enough for you.
Junjiro Okajima
----------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: unbounded disk usage for xino file
To: Jason Lunz <[EMAIL PROTECTED]>,
aufs-users <aufs-users@lists.sourceforge.net>
Date: Thu, 29 Nov 2007 12:43:09 +0900
> > If the xino code had a way to garbage-collect the unused mappings it
> > would be safe to use with tmpfs.
>
> I'll try, but I am not sure it will succeed.
Here is patch for it, which introduces two new re-mount options,
- trunc_xino=<branch path>
- itrunc_xino=<branch index>
ex. sudo mount -o remount,itrunc_xino=0 /your/aufs
Please try it and let me know the result.
It may take a long time if your xino file for the branch is very large.
I am considering another interface/option, such like
- truncate xino files for all branches unconditioanlly.
- search tmpfs (or specified fstype) branch, and truncate xino for the
selected branches only.
If you have some idea, let me know it too.
Junjiro Okajima
----------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: unbounded disk usage for xino file
To: Jason Lunz <[EMAIL PROTECTED]>
Date: Fri, 30 Nov 2007 11:07:03 +0900
Jason Lunz:
> Thanks, but for my purposes being able to do this manually isn't really
> useful. I need a fixed bound on the amount of space the xino mapping can
> use.
>
> If you can do something like that it would be great, but I think I'm ok
> for now just running with noxino. SMP-safety is my biggest concern,
> actually.
Then how about this approache?
- introduce mount options, trunc_xino and notrunc_xino.
- introduce two predefined values BeginTruncXino per a branch and
TruncXinoStep.
- when you specify trunc_xino and the number of blocks of xino exceeds
BeginTruncXino, the internal truncation will be invoked automatically.
- after the truncation, if the size is not changed, then BeginTruncXino
for that xino will be added by TruncXinoStep, in order to repeat the
same truncation.
- the default is notrunc_xino, so the default aufs behaviour is
unchanged.
- BeginTruncXino is 64, TruncXinoStep is 4, both are in blocks.
- this behavour is available only for the predefined branch filesystem
type, which is tmpfs only currently. but I am afraid other filesystem
type will be needed in the future.
- this behaivour will be available only linux-2.6.18 and later.
Junjiro Okajima
----------------------------------------------------------------------
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
