From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Genimage last partition size issue
Date: Thu, 26 May 2016 23:08:34 +0200 [thread overview]
Message-ID: <20160526210834.GA3606@free.fr> (raw)
In-Reply-To: <8737p460v7.fsf@dell.be.48ers.dk>
All,
On 2016-05-26 22:05 +0200, Peter Korsgaard spake thusly:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> > Hello,
> > On Thu, 26 May 2016 21:54:08 +0200, Peter Korsgaard wrote:
>
> >> Can dd detect and do something sensible about sparse files? I thought it
> >> was only able to create sparse files (by seeking)? I would guess you
> >> need a tool that understand the filesystem to know if you can really
> >> skip sequences of zeros when writing.
>
> > man dd(1):
>
> > sparse try to seek rather than write the output for NUL input blocks
>
> > So it doesn't seem to need a sparse file, it's just that it detects
> > blocks that are completely zero and does not write them.
>
> Yes, but you cannot safely use that. What if you have a file on your
> filesystem containing a block of zeroes? (or as part of the filesystem
> meta data like block bitmap or journal) You need to make sure that does
> get written to the card, otherwise you will read back whatever was
> written before to the card.
For the record, I was using the sparse option to dd in the past, and it
was causing a hell of a lot of filesystem corruption at runtime:
ext2/3/4 especially would cause the kernel to PANIC at best, or would
cause massive data corruption at worse.
So no, you can not use sparse when dd-ing or otherwise flashing) your
images to the target.
Beside, we explicitly state so in the manual:
https://buildroot.org/downloads/manual/manual.html#_dealing_efficiently_with_filesystem_images
Note however that flashing a filesystem image to a device while using
the sparse mode of dd may result in a broken filesystem (e.g. the block
bitmap of an ext2 filesystem may be corrupted; or, if you have sparse
files in your filesystem, those parts may not be all-zeroes when read
back). You should only use sparse files when handling files on the build
machine, not when transferring them to an actual device that will be
used on the target.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2016-05-26 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 15:26 [Buildroot] Genimage last partition size issue Matthew Weber
2016-05-24 15:56 ` Peter Korsgaard
2016-05-26 17:42 ` Matthew Weber
2016-05-26 17:49 ` Gustavo Zacarias
2016-05-26 18:35 ` Thomas Petazzoni
2016-05-26 18:37 ` Gustavo Zacarias
2016-05-26 18:41 ` Thomas Petazzoni
2016-05-26 18:45 ` Gustavo Zacarias
2016-05-26 19:18 ` Thomas Petazzoni
2016-05-26 19:19 ` Gustavo Zacarias
2016-05-26 19:55 ` Peter Korsgaard
2016-05-26 19:54 ` Peter Korsgaard
2016-05-26 19:59 ` Thomas Petazzoni
2016-05-26 20:05 ` Peter Korsgaard
2016-05-26 21:08 ` Yann E. MORIN [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=20160526210834.GA3606@free.fr \
--to=yann.morin.1998@free.fr \
--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