From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Ext3 is supported not well at 2.6.28 for external SD card removal
Date: Mon, 19 Oct 2009 15:38:01 +0200 [thread overview]
Message-ID: <20091019133801.GL28832@buzzloop.caiaq.de> (raw)
In-Reply-To: <28376653.255741255932756974.JavaMail.coremail@bj126app18.126.com>
On Mon, Oct 19, 2009 at 02:12:36PM +0800, tommy.hong wrote:
> hi,you can try EXT4!ext3 is not stable in arm,one of my friends need some ext3 bug in 2.6.25,can cause system halt!
What kind of bug are you referring to? Did you speak to the vfs/ext3
people about that?
We've been using ext3 on ARM on mass storage media for quite some time,
without facing any serious issues.
Daniel
next prev parent reply other threads:[~2009-10-19 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 5:38 Ext3 is supported not well at 2.6.28 for external SD card removal Peter Chen
2009-10-19 5:59 ` Marek Vasut
2009-10-19 6:12 ` tommy.hong
2009-10-19 13:38 ` Daniel Mack [this message]
2009-10-19 15:03 ` Russell King - ARM Linux
2009-10-20 5:34 ` Peter Chen
2009-10-20 7:33 ` Russell King - ARM Linux
2009-10-19 7:46 ` Peter Chen
2009-10-19 8:01 ` Uwe Kleine-König
2009-10-19 8:29 ` Peter Chen
2009-10-19 12:28 ` Steve Chen
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=20091019133801.GL28832@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).