public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	linux-mtd@lists.infradead.org,
	Huang Shijie <b32955@freescale.com>
Subject: Re: GPMI NAND crashes with UBIFS
Date: Thu, 18 Oct 2012 10:43:17 +0300	[thread overview]
Message-ID: <1350546197.5769.297.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CALF0-+W0SqnxBVaTHjpjTzdw-fJoQ1qHBY8u3-rMcZ6wwc7z3w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

On Wed, 2012-10-17 at 15:28 -0300, Ezequiel Garcia wrote:
> On Wed, Oct 17, 2012 at 10:21 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Wed, 2012-10-17 at 15:16 +0200, Marek Vasut wrote:
> >> Ok, I'll re-check. Though I suspect this problem disappeared with the
> >> recently
> >> applied UBI patches.
> >
> > No, you ask UBIFS to emulate a power cut, so it switched to R/O mode at
> > a random point. It printed scary error messages, which are normal
> > because an I/O operation failed. Then integck reported you the error and
> > stopped.
> >
> > All expected.
> >
> > If you use -p integck option you will just make integck _not_ fail when
> > the file-system suddenly becomes R/O, integck will just unmount it,
> > mount back, remove all its data, and start over. Then you'll get another
> > emulated power cut, and so on.
> >
> > Ideally this should never stop. The idea is to test that UBIFS can mount
> > the file-system in case of a power cut.
> >
> > If there is a problem, integck should die.
> >
> > To just stress-test your driver you do not need power-cut emulation.
> >
> 
> Is this expected behavior documented somewhere?

Sorry, no. I do not mind if someone sends a patch for mtd-www.git with
some docs WRT power-cut emulation stuff.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-10-18  7:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05  1:45 GPMI NAND crashes with UBIFS Marek Vasut
2012-10-11 11:25 ` Artem Bityutskiy
2012-10-11 11:55   ` Marek Vasut
2012-10-17 13:12     ` Artem Bityutskiy
2012-10-17 13:16       ` Marek Vasut
2012-10-17 13:21         ` Artem Bityutskiy
2012-10-17 18:28           ` Ezequiel Garcia
2012-10-18  7:43             ` Artem Bityutskiy [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=1350546197.5769.297.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=b32955@freescale.com \
    --cc=elezegarcia@gmail.com \
    --cc=fabio.estevam@freescale.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.de \
    /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