From: Rob Herring <robherring2@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V5 1/2] ext4fs ls load support
Date: Mon, 13 Aug 2012 15:30:52 -0500 [thread overview]
Message-ID: <502963FC.70706@gmail.com> (raw)
In-Reply-To: <20120813191729.37D1A202C5B@gemini.denx.de>
On 08/13/2012 02:17 PM, Wolfgang Denk wrote:
> Dear Rob Herring,
>
> In message <50294743.5010907@gmail.com> you wrote:
>>
>> I do an ubuntu install to a single ext4 fs and then ext2ls gives this:
> ...
>> The problem is in the directories with sizes of 0. It does seem to be
>
> What exactly is the problem? The listing appears pretty normal to me?
The size for the directories are 0 instead of 4096 and those directories
have no contents. An ext2ls on /usr in this example:
EXT2 rev 1, inode_size 256
ext4fs read 0 group descriptor (blkno 1 blkoff 0)
Iterate dir usr
iterate >.<
iterate >..<
iterate >lost+found<
iterate >etc<
iterate >media<
iterate >var<
iterate >usr<
ext4fs read 1760 group descriptor (blkno 14 blkoff 3072)
Note only debug messages are printed. Not even '.' or '..' entries.
It's only a problem when it is the /boot directory which seems to be
random from install to install.
> It seems you enabled some debug feature? Which exactly? And you get
> the same results without debug, don't you?
Just defined DEBUG on ext_common.c and ext4fs.c. It happens either way.
>
>> I haven't been able to produce a simple example just creating a bunch of
>> files and directories, so only the disk after an ubuntu install has the
>> problem.
>
> Can you upload the image somewhere? And indicate which exact
> problems we should look for?
Yes, I'll have to recreate one with a reasonable size.
Rob
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2012-08-13 20:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 17:39 [U-Boot] [PATCH 1/2] ext4fs ls load support uma.shankar at samsung.com
2011-12-15 22:48 ` Graeme Russ
2011-12-16 16:30 ` Mike Frysinger
2011-12-28 2:22 ` [U-Boot] [PATCH V3 " uma.shankar at samsung.com
2012-01-05 15:25 ` Wolfgang Denk
2012-01-05 15:32 ` Wolfgang Denk
2012-01-08 4:26 ` Mike Frysinger
2012-01-09 17:54 ` [U-Boot] [PATCH V4 " uma.shankar at samsung.com
2012-03-22 15:49 ` Rob Herring
2012-03-27 15:10 ` Rob Herring
2012-05-25 15:51 ` [U-Boot] [PATCH V5 " Uma Shankar
2012-08-09 21:50 ` Wolfgang Denk
2012-08-09 23:52 ` Rob Herring
2012-08-10 0:07 ` Marek Vasut
2012-08-10 6:24 ` Wolfgang Denk
2012-08-13 11:52 ` Wolfgang Denk
2012-08-13 18:28 ` Rob Herring
2012-08-13 19:17 ` Wolfgang Denk
2012-08-13 20:30 ` Rob Herring [this message]
2012-09-02 11:36 ` Wolfgang Denk
2012-09-02 16:48 ` Marek Vasut
2012-09-02 21:34 ` Rob Herring
2012-09-12 22:49 ` Tom Rini
2012-09-12 22:57 ` Rob Herring
2012-09-13 0:53 ` Tom Rini
2012-09-13 9:20 ` Marek Vasut
2012-09-13 14:29 ` Tom Rini
2012-09-20 18:34 ` Tom Rini
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=502963FC.70706@gmail.com \
--to=robherring2@gmail.com \
--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