From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: udev problems on angstrom-2008.1
Date: Mon, 28 Sep 2009 23:01:52 -0400 [thread overview]
Message-ID: <20090929030152.GA7383@denix.org> (raw)
In-Reply-To: <200909281752.11487.anarsoul@gmail.com>
On Mon, Sep 28, 2009 at 05:52:05PM +0300, Vasily Khoruzhick wrote:
> Hi, I'm experiencing problems with image for rx1950 PDA (s3c2442-based PDA
> with 32M of RAM) built by openembedded.
> For some reason, udev doesn't work, and complains about lack of free space on
> /dev (which is tmpfs) like this:
>
> udevd-event[1918]: mknod(/dev/vcS, 020660, (7,0) failed: No space left on
> device.
Been there, done that.
Short answer - you have too many requested devnodes for udev to handle within
32MB of RAM. If you absolutely need all the devices enabled in the kernel
(try disabling/reducing LEGACY_PTY), consider replacing udev with mdev (or
static devnodes). Or try moving udev's database from tmpfs into another
partition, maybe on flash.
Long answer - udev besides creating the actual devnodes also keeps its
database in the same tmpfs filesystem. It consists of an internal directory
structure with symlinks (a la sysfs) and is stored in /dev/.udev
Keeping all that in tmpfs is not efficient, as it wastes inodes and apparently
inodes in tmpfs/ramfs are the size of a memory page (4KB). By default tmpfs is
limited to half the RAM, which in your case is 16MB. That would allow roughly
4000 inodes. You definitely need more, because of the above messages. Even if
you fit all of them, using half of your available RAM just for udev is a total
waste. So, consider suggestions above.
--
Denys
next prev parent reply other threads:[~2009-09-29 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 14:52 udev problems on angstrom-2008.1 Vasily Khoruzhick
2009-09-29 3:01 ` Denys Dmytriyenko [this message]
2009-09-29 6:11 ` Vasily Khoruzhick
2009-09-29 9:09 ` Phil Blundell
2009-09-29 18:10 ` Denys Dmytriyenko
2009-09-29 18:37 ` Vasily Khoruzhick
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=20090929030152.GA7383@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@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 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.