[lkml]   [2003]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.5.63 bug when mounting dirty loopback ext3 filesystems
> Oops in 2.6.63 when trying to mount dirty ext3 loopback filesystems.
> The kernel is 2.6.63 with the latest (2003/02/28)acpi patches, plus a
> couple of one-liners found on the mailing-lists to help swsusp working
> (one in kernel/suspend.c, one in mm/pdflush.c, and one in
> drivers/net/8139tto.c; nothing related to filesystems)
> The computer is a Pentium IV on an intel chipset.
> I have in /data (an ext3 partition) three files containing ext3
> partitions which are mounted using loopback. For some reason, at
> shutdown time, /data is unmounted (or remounted ro) before the loopback
> partitions, and unmounting the loopback partitions fail, and those
> partitions need to get recovered on next reboot. That is not the issue,
> I will fix it when I get some time.
> The issue is that I got three identical pair of oops in a raw when trying my
> new 2.6.63 kernel. From the logs:

It is not an oops really - it is just a warning. 2.5 has a number of new
consistency checks so sometimes these are long-standing things, sometimes
they are not.

I couldn't get this to happen. Can you please come up with an exact sequence
of steps to reproduce this? Also I'd need to know what filesytem the backing
files reside on, and what size those files are, thanks.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.066 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site