All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Abernathy <jfabernathy@gmail.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: build failure on ubuntu 64bits development system
Date: Thu, 19 Jan 2012 15:11:47 -0500	[thread overview]
Message-ID: <4F187903.1050901@gmail.com> (raw)
In-Reply-To: <4F18568E.2050208@linux.intel.com>

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




  reply	other threads:[~2012-01-19 20:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 12:55 build failure on ubuntu 64bits development system James Abernathy
2012-01-18 14:30 ` James Abernathy
2012-01-18 14:42   ` James Abernathy
2012-01-18 14:51     ` Gary Thomas
2012-01-18 14:57       ` William Mills
2012-01-18 15:04         ` James Abernathy
2012-01-18 15:15           ` William Mills
2012-01-18 15:25             ` James Abernathy
2012-01-18 15:31               ` Martin Jansa
2012-01-18 16:06               ` William Mills
2012-01-18 16:17                 ` Jim Abernathy
2012-01-18 16:32                   ` Saul Wold
2012-01-18 17:05                     ` Jim Abernathy
2012-01-18 21:34                       ` Darren Hart
2012-01-19 13:55                         ` Jim Abernathy
2012-01-19 15:44                           ` William Mills
2012-01-19 17:44                           ` Darren Hart
2012-01-19 20:11                             ` Jim Abernathy [this message]
2012-01-18 21:31               ` Darren Hart
2012-01-18 15:01       ` James Abernathy

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=4F187903.1050901@gmail.com \
    --to=jfabernathy@gmail.com \
    --cc=dvhart@linux.intel.com \
    --cc=yocto@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.