Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
	 openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: "qemu-arm udevadm hwdb --update" eats swap space after build host update to openSUSE 13.2
Date: Tue, 16 Dec 2014 09:36:25 +0100	[thread overview]
Message-ID: <548FEF09.80304@dresearch-fe.de> (raw)
In-Reply-To: <lyiohcubq7.fsf@ensc-virt.intern.sigma-chemnitz.de>

On 15.12.2014 17:19, Enrico Scholz wrote:
> Steffen Sledz <sledz-mQBY8sqGERgRVMum7q6B+Q@public.gmane.org> writes:
> 
>> The first thing we observed was that the do_rootfs stage made a very
>> big load (more than 500) on the machine but the cpu's aren't working
>> for 100%. I could track down the problem to the call
>> ...
>> which eats swap space without end till the system crashes (more than 100GB swap space ist available).
>>
>> I've no idea how to inspect this problem further. Any ideas?
> 
> I had a similar issue when /var/tmp in the rootfs was an absolute symlink
> pointing to toplevel /var/tmp which contained some millions of files.
> 
> Can you look (lsof) which files are open by qemu?

Crazy! This really seems to be the problem.

I had a big subtree from earlier local openSUSE Build Service runs below toplevel /var/run. After deleting this the build succeeds.

But manually deleting such files before running OE builds cannot really be a reasonable solution. :(

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058


  reply	other threads:[~2014-12-16  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 10:54 "qemu-arm udevadm hwdb --update" eats swap space after build host update to openSUSE 13.2 Steffen Sledz
2014-12-15 11:00 ` Gaurang Shastri
2014-12-16  6:30   ` Steffen Sledz
2014-12-15 16:19 ` Enrico Scholz
2014-12-16  8:36   ` Steffen Sledz [this message]
2014-12-18 10:09     ` Richard Purdie
2014-12-18 11:19       ` Enrico Scholz
2015-01-01  2:45         ` Khem Raj
     [not found] <548EF838.7000705@zone42.org>
2014-12-15 15:15 ` Steffen Sledz

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=548FEF09.80304@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox