All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Pierre Ossman <drzeus-mmc@drzeus.cx>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: MMC/SD Root filesystem suspend/resume problems
Date: Wed, 25 Jul 2007 20:20:42 +0100	[thread overview]
Message-ID: <1185391242.6190.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20070725190115.GB10208@ucw.cz>

On Wed, 2007-07-25 at 19:01 +0000, Pavel Machek wrote:
> > I enabled the MMC_UNSAFE_RESUME option and the problems I was seeing was
> > "fixed". I think having this option is a bad idea (in its current form)
> > as it doesn't actually stop filesystem corruption.
> > 
> > With the option disabled, if a filesystem is mounted when you suspend my
> > tests show the filesystem is corrupted. At least if the option is
> > enabled, the filesystem is only corrupted if you remove the card whilst
> > suspended which is more preferable.
> 
> Are we talking _corruption_ here, or are we talking 'the kind of
> corruption recoverable by fsck that happens on powerfail'?

There was more damage to the system than just a dirty bit set. Yes, fsck
could fix it but I don't think it should happen in the first place...

Richard


  reply	other threads:[~2007-07-25 19:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 15:53 MMC/SD Root filesystem suspend/resume problems Richard Purdie
2007-07-19 16:42 ` Richard Purdie
2007-07-19 17:03 ` Pierre Ossman
2007-07-22 13:18   ` Richard Purdie
2007-07-22 14:05     ` Pierre Ossman
2007-07-22 14:28       ` Richard Purdie
2007-07-22 14:59         ` Pierre Ossman
2007-07-25 19:01     ` Pavel Machek
2007-07-25 19:20       ` Richard Purdie [this message]
2007-07-25 22:47         ` Pavel Machek

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=1185391242.6190.17.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.