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: Tue, 2 Aug 2011 12:57:57 -0400 [thread overview]
Message-ID: <20110802165757.GD2967@thunk.org> (raw)
In-Reply-To: <20110802160715.3069.qmail@web4212.mail.ogk.yahoo.co.jp>
On Wed, Aug 03, 2011 at 01:07:08AM +0900, Round Robinjp wrote:
> So that means I have thrown away some important part of
> the filesystem when I did truncate -s 1G, isn't it?
> Will things go wrong if I flash this 1G image to my eMMC
> partition (without using Yongqiang's new 64bit resize patches)?
> I need to understand whether Yongqiang's patch is absolutely
> necessary for this purpose or just a good thing to have.
This is one of the reasons why I originally suggested using zero_free
and make_sparse to write the file system image. It's a much, much,
MUCH simpler way of handling things, and it doesn't require resizing
the file system image, using truncate (and making sure you truncate to
the right size, etc.).
With the method Amir talked about, it matters whether or not the file
system is mounted when you use resize2fs, whether you have the latest
resize patches, etc., etc.
- Ted
next prev parent reply other threads:[~2011-08-02 16:58 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
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 [this message]
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=20110802165757.GD2967@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).