Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Woody Wu <narkewoody@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ubifs rootfs attached error
Date: Wed, 14 Aug 2013 06:12:17 +0800	[thread overview]
Message-ID: <20130813221217.GA18527@zuhnb712> (raw)
In-Reply-To: <520A7922.2050703@gmail.com>

On Tue, Aug 13, 2013 at 08:21:22PM +0200, Stefan Peter wrote:
> On 13.08.2013 16:08, Woody Wu wrote:
> 
> > Stefan, thanks for the hints.  Yes, my kernel configuration disalbed the
> > NAND ECC. I like to study on that. But, do you think this is reason why
> > my ubifs did not get attached? Thanks.
> 
> Yes, definitively. I don't want to say that there are no other problems
> in your setup, but as long as you can not read back exactly what you
> have written to the flash, there is very little chance that UBI will work.
> UBIFS is based upon MTD. And MTD relies on a working FLASH driver. As
> long as one of these layers does not work properly, the topmost (UBIFS)
> layer can not work properly, either.
> 

If so, that's really wired. Since befor trying the ubifs, the same
kernel was actually running jffs2 as rootfs without a sign that there is
a i/o problem. Just because the performance concerns to jffs2, I decided
to try ubifs.


-- 
I can't go back to yesterday - because I was a different person then

  reply	other threads:[~2013-08-13 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 13:04 [Buildroot] ubifs rootfs attached error Woody Wu
2013-08-13 13:39 ` Stefan Peter
2013-08-13 14:08   ` Woody Wu
2013-08-13 18:21     ` Stefan Peter
2013-08-13 22:12       ` Woody Wu [this message]
2013-08-13 16:44 ` Arnout Vandecappelle

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=20130813221217.GA18527@zuhnb712 \
    --to=narkewoody@gmail.com \
    --cc=buildroot@busybox.net \
    /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