From: William Mills <wmills@ti.com>
To: Jim Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org, Darren Hart <dvhart@linux.intel.com>
Subject: Re: build failure on ubuntu 64bits development system
Date: Thu, 19 Jan 2012 10:44:51 -0500 [thread overview]
Message-ID: <4F183A73.2060901@ti.com> (raw)
In-Reply-To: <4F1820DE.7060700@gmail.com>
On 01/19/2012 08: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.
This looks pretty important to me. Can you create a bug report for this
Jim? It may be decided that it is a dup of the one Darren already
pointed to but I would like to see someone prove that. It is not clear
to me why the blockstats feature could not be supported on btrfs so
could justify seperate tracking anyway. (The resolution of the one
Darren pointed to will be to just disable blockstats for filesystem that
don't have block devices.)
> 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.
>
> Jim A
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-01-19 15:44 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 [this message]
2012-01-19 17:44 ` Darren Hart
2012-01-19 20:11 ` Jim Abernathy
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=4F183A73.2060901@ti.com \
--to=wmills@ti.com \
--cc=dvhart@linux.intel.com \
--cc=jfabernathy@gmail.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.