From: Theodore Tso <tytso@mit.edu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-ext4@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: Problem mounting ext2 using ext3?
Date: Tue, 6 May 2008 08:05:44 -0400 [thread overview]
Message-ID: <20080506120544.GB6918@mit.edu> (raw)
In-Reply-To: <19f34abd0805060026m138bf3dfo87dbf303362d69ca@mail.gmail.com>
On Tue, May 06, 2008 at 09:26:30AM +0200, Vegard Nossum wrote:
>
> I posted a very similar problem a couple of days ago:
> http://www.nabble.com/BUG-in-ext3_sync_fs-td16999997.html
>
> to which I got zero replies. Can I close this in my internal bugzilla
> as dup/"not my fault"? The stacktrace looks very similar. This was
> also ext2 fs mounted (apparently) by ext3 code.
Yeah, sorry, I didn't have network access when I looked at your
e-mail, and so I didn't see the stack trace until you pointed at the
mail message again. Because you mentioned a USB stick, I assumed it
was the problem with a USB stick getting pulled or being loose causing
an I/O error leading to an oops problem, and I missed the hint of the
problem occurring in the ext3 code when you were using an ext2
formattem. Fortunately when Geert reported the bug a second time, I
was less dense at the time, and figured it out quickly. :-)
- Ted
next prev parent reply other threads:[~2008-05-06 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 21:11 Problem mounting ext2 using ext3? Geert Uytterhoeven
2008-05-05 22:26 ` Theodore Tso
2008-05-06 7:11 ` Geert Uytterhoeven
2008-05-06 7:26 ` Vegard Nossum
2008-05-06 7:26 ` Vegard Nossum
2008-05-06 9:50 ` Jan Kara
2008-05-06 12:05 ` Theodore Tso [this message]
2008-05-06 10:02 ` Jan Kara
2008-05-06 10:02 ` Jan Kara
2008-05-06 11:20 ` Geert Uytterhoeven
2008-05-06 19:05 ` Geert Uytterhoeven
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=20080506120544.GB6918@mit.edu \
--to=tytso@mit.edu \
--cc=geert@linux-m68k.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.