Fran ois:
> However, I switched to 3.10.28 that got out on sunday, so we can be
> quite sure the kernel is the right one. I also applied the b.patch to
> check for msg on boot.
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.
int au_test_loopback_overlap(struct super_block *sb, struct dentry *h_adding)
{
:::
43 BUG_ON(!l);
pr_info("lo {num %d, f 0x%x, fname %.*s, file %p, vfile %p, state
%d}\n",
l->lo_number, l->lo_flags,
LO_NAME_SIZE, l->lo_file_name,
l->lo_backing_file, l->lo_backing_virt_file,
l->lo_state);
44 BUG_ON(!l->lo_backing_file);
:::
}
We will get something like this.
aufs 3.10.x
debugging au_test_loopback_overlap [aufs]
aufs au_test_loopback_overlap:35:mount[6835]: lo {num 0, f 0x5, fname
/run/shm/sq.img, file ffff88002d3b1b00, vfile (null), state 1}
> The find command you gave me is invalid (find: unrecognized: -ls),
> however the filesystem is mounted and appears OK:
>
> (initramfs) ls /filesystem.squashfs/
> bin etc media root sys
> boot home mnt sbin tmp
> commsmundi lib opt selinux usr
> dev lib64 proc srv var
> (initramfs)
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.
J. R. Okajima
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
