Jacek Konieczny:
> Unfortunately, I don't have those logs around any more.
> I have rebuilt the system to use 'noxino' option to mount aufs instead.
> So far - so good...
Of course it is your choice. And I hope you would understand the demerit
of noxino.
I guess why your XINO files were not truncated is just because of the
size of your tmpfs and the number of inodes on your branch fs.
During the truncation, the XINO file is copied with making a "hole",
such like this.
loop {
read(src, buffer, 4096);
if (buffer is all zero)
lseek(dst, 4096);
else
write(dst, buffer, 4096);
}
During this copy, the fs where the XINO file is located needs to have
the free space almost twice as the current size of XINO.
If the current size of your XINO is 5MB and the free space of its FS is
10MB, then you MAY success. But obviously you are in danger. When some
other processes create/write/modify any file on the fs, then you will
fail.
My recommendation is to estimate the size of XINO, prepare large enough
to hold XINO, and specify it by "xino=". The aufs manual will help you
to estimate.
J. R. Okajima
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
