Hi Junjiro,
> Then I want to know the status of "struct loop_device" object.
> Would you apply this patch manually? It will print some info just before
> hitting kernel BUG.
Here is the output. There are some non-printable "filled-squarish"
characters after "fname" that I replace by "#":
aufs 3.10.x-20140120
debugging au_test_loopback_overlap [aufs]
loop: AES key scrubbing enabled
loop: loaded (max 8 devices)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
aufs au_test_loopback_overlap:48:exe[289]: lo {num 0, f 0x200003, fname
######/live/image/live/filesystem.squashfs, file (null), vfile
ffff88000340c000, state -30720}
------------[ cut here ]------------
kernel BUG at fs/aufs/loop.c:49!
[...]
> Ah, you are using busybox or something.
> Then "find | xargs stat > /dev/null" will be ok.
> But I don't think it necessary since your /filesystem.squashfs looks
> fine.
Yes indeed, using busybox. I don't seem to have "stat" either, remember
I'm working on a minimal initramfs:
"/bin/sh: stat: not found"
Thanks,
François.
------------------------------------------------------------------------------
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
