Fran ois: > Appart from your patches, I only apply IMQ and NDPI (also attached), but > I don't think the issue is related.
Agreed.
> > And may I ask you trying one more debug print patch?
>
> Of course, but you didn't attach the patch!
Here it is.
It will print the size of the object from several places.
All the printed sizes should be equal, like this.
$ dmesg | fgrep -w lo
loop_init:1929: lo 672
loop_set_fd:959: lo 672
loop_set_fd:959: lo 672
aufs au_test_loopback_overlap:31:mount[4211]: lo 672
aufs au_test_loopback_overlap:36:mount[4211]: lo {num 0, f 0x5, fname
/run/shm/sq.img, file ffff88002dbf6500, vfile (null), state 1}
It means the size of the object 672 bytes on my test system, and mathces
the value from au_test_loopback_overlap().
Please insert "dmesg | fgrep -w lo" (or something) just before mounting
aufs in your script. I'd like to compare the value from
au_test_loopback_overlap().
J. R. Okajima
d.patch.bz2
Description: BZip2 compressed data
------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
