Dear Junjiro, thanks for your answer in lightspeed.
On Thursday 23 June 2011, 16:32:45 sf...@users.sourceforge.net wrote: > Hi Pete, > > "Hans-Peter Jansen": > > I hesitated a lot to report this bug, since it concerns a pretty > > old setup but the pain it causes is too strong to live with it.. I > > know, you're quite short of time for aufs, but hopefully you're > > able to look into it sometimes. > > Don't worry about that. > I remember you have supported aufs for a long time. aufs2 plays a major role for my diskless setups (apart from bog standard kernel technology..). > > Due to a motorbike accident, I stayed in a hospital for the last > > three weeks, and was glad to get back home by the end of last week. > > Since I still depend on moving by wheelchair for at least a few > > more weeks, my office a floor down is hard to reach (suffering from > > a humerus head and tibia head fracture with compartment syndrome). > > I am very sorry. Unfortunately my poor English doesn't allow me to > say good words, but I can only say I hope you get better soon. Thanks for your kind words. > > Thanks to an aufs2 based diskless setup, I was able to create a > > tentative workplace quickly. The setup is a bit dated (openSUSE > > 11.1), but most of > > > > Before collecting data for this report, I updated aufs2 to the > > current git version. With default config (debug enabled), the > > system didn't boot successfully, due to a triggering DyDbgSize in > > dy_vmop() in dynop.c:226 (I have photos of this issue only). > > Disabling aufs2 debug "resolved" this for me, but doesn't raise > > confidence.. > > The aim of dynop.c:226 is to detect the local changes in struct > vm_operations_struct. "local" means distribution specific. > I looked openSUSE 11.2 (instead of 11.1) which contains > linux-2.6.31.5-0.1, and found suse people added some fields into > struct vm_operations_struct. So if you apply this patch to your aufs > source file, then the compilation will success at least. Well, compilation of the standalone version succeeded before, but failed on boot.. With the patch applied and debug enabled, the boot succeeded again, and I wasn't able to provoke a crash since then. Great. > But I am not sure whether the crash problem will be solved too, since > I don't remember the old version you are using. If the cause of your > problem is new to me, then the patch may not solve it. Let's hope, that it will not happen again in the next days. > Anyway I'd suggest you to upgrade to latest aufs2.1-31 I did that already before reporting the problem, of course. > and apply this > patch first. If you meet the problem, then let me know again. I know > your condition is not good, so you don't need to hurry. Will call back the next days in any case to keep you informed. > > Take care > J. R. Okajima A big thank you for this great support, Junjiro. Pete ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev
