All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: George Hilliard <gh403@msstate.edu>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Large rootfs corrupted by build system
Date: Thu, 6 Feb 2014 00:02:29 -0200	[thread overview]
Message-ID: <CAP9ODKqv=Dasqke-Ox_nPgCZzF69CAq56fnCRjsYzYMdiRtGWA@mail.gmail.com> (raw)
In-Reply-To: <7038837.RuQbIyRRBY@shillig-arch>

Hello George,

On Sun, Feb 2, 2014 at 6:19 AM, George Hilliard <gh403@msstate.edu> wrote:
> I have run into a very odd issue when building a custom Yocto "dora" image for the i.MX6 SABRE Auto.  When building a small image (final image is around 80MB), the image is generated just fine.  However, when I build a much larger image (around 2GB), the root filesystem is generated corrupt!  This is not a fluke; every time I regenerate the image, it is corrupt (according to fsck).

The 'fsck' information is interesting. How did you figure out this?
Does it happens during first boot?

Another question, did you try to use the generated ext3 file and make
the sdcard byhand to be sure it is generated fine? We need to isolate
the root cause being the 'sdcard' generation class or a ext3 utility
bug.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


      reply	other threads:[~2014-02-06  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02  8:19 Large rootfs corrupted by build system George Hilliard
2014-02-06  2:02 ` Otavio Salvador [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='CAP9ODKqv=Dasqke-Ox_nPgCZzF69CAq56fnCRjsYzYMdiRtGWA@mail.gmail.com' \
    --to=otavio@ossystems.com.br \
    --cc=gh403@msstate.edu \
    --cc=meta-freescale@yoctoproject.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 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.