From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] Need help with genimage
Date: Sun, 08 Jan 2017 19:32:37 +0100 [thread overview]
Message-ID: <1483900357.4757.3.camel@embedded.rocks> (raw)
In-Reply-To: <20170108174537.jaz3hgr6zau623r7@tarshish>
Hi Baruch,
On Sun, 2017-01-08 at 19:45 +0200, Baruch Siach wrote:
> Hi J?rg,
>
> On Sun, Jan 08, 2017 at 12:58:51PM +0100, J?rg Krause wrote:
> > I am able to generate the sd card image and copy it to the sd card
> > using Suses imagewriter. The board boots fine. However, the rootfs
> > size
> > is not 512MB as expected:
> >
> > # df -hT
> > Filesystem???????????Type????????????Size??????Used Available Use%
> > Mounted on
> > /dev/root????????????ext4???????????38.7M?????37.9M?????????0 100%
> > /
> > devtmpfs?????????????devtmpfs??????501.9M?????????0????501.9M???0%
> > /dev
> > tmpfs????????????????tmpfs?????????502.4M?????????0????502.4M???0%
> > /dev/shm
> > tmpfs????????????????tmpfs?????????502.4M??????3.9M????498.4M???1%
> > /tmp
> > tmpfs????????????????tmpfs?????????502.4M?????24.0K????502.4M???0%
> > /run
> >
> > I am not able to create any file larger file on the filesystem nor
> > start some programs.
> >
> > What am I missing here? Can somebody enlighten me please :-)
>
> Unless you set BR2_TARGET_ROOTFS_EXT2_BLOCKS and
> BR2_TARGET_ROOTFS_EXT2_INODES?
> you'll get a minimal ext2/3/4 filesystem with no free space.
> Alternatively,?
> you may run on target the resize2fs tool from the e2fsprogs package
> on the?
> root filesystem to expand the filesystem to the size of the
> partition.
Which values should I use for blocks and inodes if I set the rootfs
size to 512M in genimage.cfg? Any suggestions?
J?rg
next prev parent reply other threads:[~2017-01-08 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 11:58 [Buildroot] Need help with genimage Jörg Krause
2017-01-08 17:45 ` Baruch Siach
2017-01-08 18:32 ` Jörg Krause [this message]
2017-01-08 19:02 ` Baruch Siach
2017-01-08 19:07 ` Jörg Krause
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=1483900357.4757.3.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/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