From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Setting custom PTXDIST_TEMPDIR for large image gen?
Date: Wed, 10 Apr 2013 07:55:23 +0200 [thread overview]
Message-ID: <20130410055523.GI32214@pengutronix.de> (raw)
In-Reply-To: <20130410054745.GH32214@pengutronix.de>
On Wed, Apr 10, 2013 at 07:47:45AM +0200, Michael Olbrich wrote:
> On Tue, Apr 09, 2013 at 09:07:57PM +0200, Erwin Rol wrote:
> > On 9-4-2013 20:55, Michael Olbrich wrote:
> > > On Tue, Apr 09, 2013 at 05:49:11PM +0200, Dennis.Herbrich@hytera.de wrote:
> > >> I configured ptxdist 2013.03.0 to generate a rather large (8GB) hd.img for
> > >> me,
> > >> but genext2fs fails:
> >
> > Last time I tried to use genext2fs it was not capable of generating
> > images larger than 2G (or was it 4G), cause I also needed 8G.
>
> On a 32bit host system? Probably 2.xG. genext2fs seems to map the whole
> Image, so the limit is you're virtual address space. Hmm, I tried a 6G
> image here. I could create it, but it seems to be broken.
> Why would you need such a large image anyways? Unless you have that much
> contents initially, starting smaller and running resize2fs when booting for
> the first time is better.
Btw, if you know any good alternative for genext2fs then I'd be happy to
hear about it. I know there are limitations. genext2fs cannot create ext4
images, so we can't take advantage of the new features for the initial
files. I don't know if there is a performance impact here. And so far I
have found no way to add extended attributes.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-04-10 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 15:49 Dennis.Herbrich
2013-04-09 18:55 ` Michael Olbrich
2013-04-09 19:07 ` Erwin Rol
2013-04-10 5:47 ` Michael Olbrich
2013-04-10 5:55 ` Michael Olbrich [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=20130410055523.GI32214@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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