From: "Brüns, Stefan" <Stefan.Bruens@rwth-aachen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ext4: crash when writing a file
Date: Tue, 29 Nov 2016 12:14:38 +0000 [thread overview]
Message-ID: <2757307.t5dS6qHjZC@sbruens-linux> (raw)
In-Reply-To: <9c9637dd-582d-ac8a-fb71-ee5dcb8307bb@armadeus.com>
On Dienstag, 29. November 2016 10:50:45 CET you wrote:
> Hello,
>
> I am working on a i.MX6UL based board with a 4GB eMMC partitioned as
> following:
>
> Device Boot Start End Sectors Size Id Type
> /dev/sdb1 2048 264191 262144 128M 83 Linux
> /dev/sdb2 264192 4458495 4194304 2G 83 Linux
> /dev/sdb3 4458496 7634943 3176448 1.5G 83 Linux
>
> On the 2nd partition, I write this ext4 filesystem file generated by
> Buildroot:
> Filesystem volume name: "ROOTFS"
> Last mounted on: <not available>
> Filesystem UUID: b9833a36-e89d-429a-b120-c3b00bcb7785
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: has_journal dir_index filetype extent
> sparse_super uninit_bg
> Filesystem flags: signed_directory_hash
> Default mount options: (none)
> Filesystem state: clean
> Errors behavior: Unknown (continue)
> Filesystem OS type: Linux
> Inode count: 3456
> Block count: 91756
91756 blocks ...
> Reserved block count: 4587
> Free blocks: 13458
> Free inodes: 488
> First block: 1
> Block size: 1024
1k each -> 91 MByte filesystem
> Fragment size: 1024
> Blocks per group: 7648
> Fragments per group: 7648
> Inodes per group: 288
> Inode blocks per group: 36
> Last mount time: n/a
> Last write time: Tue Nov 29 09:44:52 2016
> Mount count: 0
> Maximum mount count: -1
> Last checked: Tue Nov 29 09:44:52 2016
> Check interval: 0 (<none>)
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> First inode: 11
> Inode size: 128
> Journal inode: 8
> Default directory hash: half_md4
> Directory Hash Seed: a583a07f-6b59-442d-8e08-9be305f78d17
> Journal backup: inode blocks
>
> This filesystem is written with the following commands:
>
> BIOS> setexpr nbblocks ${filesize} / 0x200
> BIOS> setexpr nbblocks ${nbblocks} + 1
> BIOS> mmc write ${loadaddr} 0x40800 ${nbblocks}
> MMC write: dev # 0, block # 264192, count 183513 ... 183513 blocks
> written: OK
>
> I can boot Linux with it without any issues, however if I try to write a
> file in it I get the following crash:
>
> BIOS> ext4write mmc 0:2 ${loadaddr} /boot/${kernelimg} ${filesize}
What are you trying to achieve here? What is the value of $filesize?
Btw, which u-boot version are you using?
Regards,
Stefan
next prev parent reply other threads:[~2016-11-29 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 9:50 [U-Boot] ext4: crash when writing a file Sébastien Szymanski
2016-11-29 12:14 ` Brüns, Stefan [this message]
2016-11-29 13:10 ` Sébastien Szymanski
2016-11-29 14:38 ` Brüns, Stefan
2016-11-29 15:23 ` Sébastien Szymanski
2016-12-11 17:10 ` Stefan Bruens
2017-01-20 17:32 ` Sébastien Szymanski
2017-01-23 16:38 ` Brüns, Stefan
2017-01-24 9:58 ` Sébastien Szymanski
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=2757307.t5dS6qHjZC@sbruens-linux \
--to=stefan.bruens@rwth-aachen.de \
--cc=u-boot@lists.denx.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