From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.216.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4762CE00599 for ; Thu, 19 Jan 2012 12:11:49 -0800 (PST) Received: by qcsp19 with SMTP id p19so232106qcs.35 for ; Thu, 19 Jan 2012 12:11:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=pMQjsuXTquLFmnG6yY9oasMWI8HSadh+/a5qgBcWf4g=; b=F768KzucwCrUbFhl2LBnAha2d01i73HDWW/TANME1XcCfWZ4HSDecAMb9n4RMyfrRm SlCKdIGIhUK3jVMewYqQ71GIHNByBbEska8BhCBv05M0U6uM7p7UFXH6348esPSx4q3F hen+N47yOPid4+dgI2yqPeRSOpBvnbmHeO+ps= Received: by 10.224.45.6 with SMTP id c6mr29155479qaf.62.1327003908528; Thu, 19 Jan 2012 12:11:48 -0800 (PST) Received: from [10.0.1.54] (nc-184-3-54-63.dhcp.embarqhsd.net. [184.3.54.63]) by mx.google.com with ESMTPS id dh10sm1674159qab.19.2012.01.19.12.11.47 (version=SSLv3 cipher=OTHER); Thu, 19 Jan 2012 12:11:47 -0800 (PST) Message-ID: <4F187903.1050901@gmail.com> Date: Thu, 19 Jan 2012 15:11:47 -0500 From: Jim Abernathy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: Darren Hart References: <4F16DC5D.9070903@mlbassoc.com> <4F16DDCD.2020701@ti.com> <4F16E20C.9010909@ti.com> <4F16EE0D.1080805@ti.com> <4F16F0A2.9070805@gmail.com> <4F16F410.4050800@linux.intel.com> <4F16FBBF.6080406@gmail.com> <4F173AD5.4040200@linux.intel.com> <4F1820DE.7060700@gmail.com> <4F18568E.2050208@linux.intel.com> In-Reply-To: <4F18568E.2050208@linux.intel.com> Cc: yocto@yoctoproject.org Subject: Re: build failure on ubuntu 64bits development system X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 20:11:49 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 01/19/2012 12:44 PM, Darren Hart wrote: > > On 01/19/2012 05:55 AM, Jim Abernathy wrote: >> On 01/18/2012 04:34 PM, Darren Hart wrote: >>> On 01/18/2012 09:05 AM, Jim Abernathy wrote: >>> >>>> FYI for those wanting to use Soft RAID, make sure you create one very >>>> small primary partition for GRUB2 to put the second part of the >>>> boot-loader in. Can't use the old process. >>> I strongly recommend using a separate DISK for your OS installation. >>> Yocto builds are hard on disks, and RAID 0 increases your risk of >>> failure in exchange for the added performance. I use a small SSD for my >>> OS disk and a large RAID0 array of spinning disks for /build and another >>> array for /virt (where my VM images live - easily recreated). >>> >> Learned a few things in this process. I appreciate all the help and advice. >> >> 1. So we know that at least with Edison, btrfs does not work with bitbake. >> 2. When I rebuilt the system, this time I put the Linux root directory >> on an 80GB SSD. That is where I also have my clone of Linux-Yocto >> repository, poky, and download directory , DL_DIR. >> 3. I have create /build with EXT4 format on a Software RAID 0 (striped) >> partition, using 2 separate hard drives, to use as the working >> build directory for bitbake. I have a striped swap file on the same >> two drives. But with 8GB or RAM, I shouldn't be using that much. >> >> My build times for some of the basic meta-intel BSPs is around 103 minutes. > You may be able to improve upon that with the following in /etc/fstab: > > /dev/md0 /build ext4 noauto,noatime,nodiratime,commit=6000 0 2 > > This reduces the number of writes due to updated access time and > increases the commit interval so it doesn't stall while writing out > every 5 minutes per default. > > NOTE: THIS INCREASES YOUR RISK OF DATA LOSS > > If your machine goes down during a build, you should plan on formatting > that drive. If you only keep builds on it, they easily recreateable and > you may find the performance boost is worth the risk. > I'll test this out and see. I'm plan on keeping this system on a UPS anyway. Jim S