From: schen@mvista.com (Steve Chen)
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 07:28:08 -0500 [thread overview]
Message-ID: <1255955288.3153.219.camel@linux-1lbu> (raw)
In-Reply-To: <4ADC234F.8070505@gmail.com>
On Mon, 2009-10-19 at 16:29 +0800, Peter Chen wrote:
> Uwe Kleine-K?nig wrote:
> > Hello,
> >
> > On Mon, Oct 19, 2009 at 03:46:11PM +0800, Peter Chen wrote:
> >> Marek Vasut wrote:
> >>> Dne Po 19. ??jna 2009 07:38:35 Peter Chen napsal(a):
> >>> You popped the card out without unmounting the filesystem I guess ?
> >> We don't execute umount at 2.6.27/23 either, and it has little error:
> >> [ 32.541208] Buffer I/O error on device mmcblk1p1, logical block 0
> >> [ 32.544784] lost page write due to I/O error on mmcblk1p1
> >>
> >> Besides, the remove card is ok after suspend at 2.6.27 and 2.6.23.
> >>
> >> Usually, the remove card(ext3) without umount is forbiddon or not?
> > You shouldn't remove the card without unmounting first. And you should
> > unmount with .23 and .27, too. Just because these kernels don't wail it
> > doesn't mean you cannot loose data.
> >
> > Best regards
> > Uwe
> >
> I find the system still will be deadlock if i use sync before go to suspend.
> I wonder why system will go to deadlock even there is not card at slot.
>
Is this specific to ext3? Does it happen to other file systems such as
xfs?
Regards,
Steve
prev parent reply other threads:[~2009-10-19 12:28 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
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 [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=1255955288.3153.219.camel@linux-1lbu \
--to=schen@mvista.com \
--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).