From: Andrew Morton <akpm@digeo.com>
To: ebrunet@lps.ens.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.63 bug when mounting dirty loopback ext3 filesystems
Date: Tue, 4 Mar 2003 11:16:26 -0800 [thread overview]
Message-ID: <20030304111626.52a64e3c.akpm@digeo.com> (raw)
In-Reply-To: <20030304144138.GA28345@lps.ens.fr>
>
> 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.
prev parent reply other threads:[~2003-03-04 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 14:41 Éric Brunet
2003-03-04 19:16 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030304111626.52a64e3c.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=ebrunet@lps.ens.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®