From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yh0-f47.google.com (mail-yh0-f47.google.com [209.85.213.47]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 72539E002AC for ; Wed, 5 Feb 2014 18:02:30 -0800 (PST) Received: by mail-yh0-f47.google.com with SMTP id c41so1374983yho.6 for ; Wed, 05 Feb 2014 18:02:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=sRdQZ8SkEa57UJx8ck+5/pT4BYYywRT/6aMzZK2H8xY=; b=Ls7j9jXqYQAAfJ4Ee0mZjTjmSCRGiDHtRqjb4xkpXR3ZXmUyBoNA5MyBcDalFafdVi 9E5Vc4U1OYY8wN1ct+95XDMDy65o9gCLZX+KetsiHopxlsNiWU/mXjualqs29CW2gaIk YpKALMyqiW+guCQLsHYn9Fx3+cj3F8NUi48kNVDIRTjOTaAgu32tbKMijeBTG1TskyED 7V5Ws7+WBtItbovLE0WAzCk62a5RBQoNSn9iJr0dgNFf2Aivt3zSReyGWlPx31wNx9hq y0mMCYWpsiT8b/XtamhbBoABWZgXhDSbiDxBal7Xq+l6+FtbTCHfsyVLoubx/6l/pL6o Fcag== MIME-Version: 1.0 X-Received: by 10.236.183.111 with SMTP id p75mr2542400yhm.148.1391652149921; Wed, 05 Feb 2014 18:02:29 -0800 (PST) Sender: otavio.salvador@gmail.com Received: by 10.170.62.84 with HTTP; Wed, 5 Feb 2014 18:02:29 -0800 (PST) In-Reply-To: <7038837.RuQbIyRRBY@shillig-arch> References: <7038837.RuQbIyRRBY@shillig-arch> Date: Thu, 6 Feb 2014 00:02:29 -0200 X-Google-Sender-Auth: 6kIlLMPHYMLBk8Th5wTrPPk6xf0 Message-ID: From: Otavio Salvador To: George Hilliard Cc: "meta-freescale@yoctoproject.org" Subject: Re: Large rootfs corrupted by build system X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 02:02:31 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello George, On Sun, Feb 2, 2014 at 6:19 AM, George Hilliard wrote: > I have run into a very odd issue when building a custom Yocto "dora" imag= e for the i.MX6 SABRE Auto. When building a small image (final image is ar= ound 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 (accordin= g 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. --=20 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