Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yi Qingliang <niqingliang2003@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: disk space problem
Date: Sun, 30 Dec 2012 23:01:23 +0800	[thread overview]
Message-ID: <2102269.34dXU5iKec@ll-pc> (raw)
In-Reply-To: <CAP9ODKrVuLGDVUPC+co_oxVRfxnamRCnLhSe4wJp-WU3HVGiuw@mail.gmail.com>

On Saturday, December 29, 2012 06:07:27 PM Otavio Salvador wrote:
> On Sat, Dec 29, 2012 at 1:09 PM, Yi Qingliang 
<niqingliang2003@gmail.com> wrote:
> > When using poky,  I got following problem:
> > 
> > WARNING: The free inode of /dev/md127 is running low (0.000K left)
> > ERROR: Immediately abort since the disk space monitor action is
> > "ABORT"!
> > ERROR: Unknown event: <bb.event.DiskFull object at 0x47dbed0>
> > 
> > the disk is  a raid partition, and fs format is reiserfs, the 'statvfs'
> > call in bitbake got a zero f_favail.
> > 
> > I don't know it is feature of reiserfs, or bug of reiserfs driver, or
> > python's problem.
> > 
> > Any idea?
> 
> I had a similar problem when using btrfs. You can find the bug at
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=3609

The only thing I can do is to disable the disk space motor.
I doubt it is some fs format's feature, but not bug.
If so, the bitbake should consider that.

> Regards,
> 
> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



      reply	other threads:[~2012-12-30 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-29 15:09 disk space problem Yi Qingliang
2012-12-29 20:07 ` Otavio Salvador
2012-12-30 15:01   ` Yi Qingliang [this message]

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=2102269.34dXU5iKec@ll-pc \
    --to=niqingliang2003@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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