From: Ted Ts'o <tytso@mit.edu>
To: Round Robinjp <roundrobinjp@yahoo.co.jp>
Cc: Goldstein Amir <amir73il@gmail.com>,
Andreas Dilger <aedilger@gmail.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: flashing large eMMC partitions with ext4
Date: Mon, 1 Aug 2011 14:57:45 -0400 [thread overview]
Message-ID: <20110801185745.GG21388@thunk.org> (raw)
In-Reply-To: <632658.72291.qm@web4207.mail.ogk.yahoo.co.jp>
On Tue, Aug 02, 2011 at 02:43:20AM +0900, Round Robinjp wrote:
> > I meant using a newer version of resize2fs (which you do not have),
>
> I have now corrected this and other mistakes.
> But when I mount the image after finally extending
> to 4G, the df still shows the size as 1G.
> Am I still doing something wrong?
This is nowhere near correct. My first recommendation is to please
read the man pages so you understand what is happening; it's pretty
clear to me that you're following some other people's suggestions
without really understanding what each step does, and you're doing
some things which they were suggesting when you are creating the
small, compressed image, and what you should do after you flash the
image onto the disk.
Let me try this with a bit more more explicitly in hopes that it is
helpful.
1) Create the file system and mount it.
dd if=/dev/zero of=a.img bs=1G count=4
mke2fs -t ext4 -O ^has_journal a.img
mount -o loop a.img /mnt
2) Populate the image with your content. (I'll leave that up to you.)
3) Unmount the file system and compress it to its minimum size.
umount /mnt
resize2fs -M a.img
4) Save a.img into your source tree, or whatever.
5) For each system that you want to install this on, assuming that
/dev/mmc is your device with the mmc:
dd if=a.img of=/dev/mmc bs=32k
resize2fs /dev/mmc
tune2fs -O has_journal /dev/mmc
You're done!
Before you try this I recommend you read through each man pages for
mke2fs, resize2fs, tune2fs, and dd so you completely understand what
all of the options are, and why it works.
- Ted
next prev parent reply other threads:[~2011-08-01 18:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 15:49 flashing large eMMC partitions with ext4 Round Robinjp
2011-07-22 16:35 ` Andreas Dilger
2011-07-25 16:34 ` Round Robinjp
2011-07-25 16:55 ` Andreas Dilger
2011-07-25 18:10 ` Ted Ts'o
2011-07-25 18:36 ` Amir Goldstein
2011-07-26 1:39 ` Yongqiang Yang
2011-07-26 4:07 ` Andreas Dilger
2011-07-26 4:13 ` Theodore Tso
2011-07-26 17:38 ` Round Robinjp
2011-07-27 1:21 ` Ted Ts'o
2011-07-27 16:40 ` Round Robinjp
2011-07-27 17:16 ` Andreas Dilger
2011-07-27 18:05 ` Amir Goldstein
2011-07-29 19:05 ` Round Robinjp
2011-07-29 19:46 ` Amir Goldstein
2011-08-01 17:43 ` Round Robinjp
2011-08-01 18:57 ` Ted Ts'o [this message]
2011-08-01 19:44 ` Amir Goldstein
2011-08-02 6:53 ` Round Robinjp
2011-08-02 7:42 ` Amir Goldstein
2011-08-02 16:07 ` Round Robinjp
2011-08-02 16:57 ` Ted Ts'o
2011-08-02 17:52 ` Amir Goldstein
2011-08-03 15:15 ` Round Robinjp
2011-08-02 17:44 ` Amir Goldstein
2011-08-03 8:40 ` Amir Goldstein
2011-08-09 16:05 ` Round Robinjp
2011-08-09 19:55 ` Amir Goldstein
2011-07-27 18:08 ` Round Robinjp
2011-07-27 19:28 ` Andreas Dilger
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=20110801185745.GG21388@thunk.org \
--to=tytso@mit.edu \
--cc=aedilger@gmail.com \
--cc=amir73il@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=roundrobinjp@yahoo.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).