public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 13:28:19 -0500	[thread overview]
Message-ID: <50294743.5010907@gmail.com> (raw)
In-Reply-To: <20120813115226.A59C9204046@gemini.denx.de>

On 08/13/2012 06:52 AM, Wolfgang Denk wrote:
> Dear Rob Herring,
> 
> In message <50244D5A.3080304@gmail.com> you wrote:
>>
>> I reported already that the prior version that ext4 has issues with
>> sub-directories. I don't think that has been addressed in V5. Some
>> directories show up fine and some don't. So it's kind of random whether
>> u-boot can read a /boot directory. This was after full ubuntu installs.
>> I'd guess a simple test with a couple of files and directories will not
>> show the problem.
> 
> We really need a test case here.  In my (certainly not very extensive)
> tests I didn't see such a problem.
> 
> Can you please describe what failed for you?
> 

I do an ubuntu install to a single ext4 fs and then ext2ls gives this:

EXT2 rev 1, inode_size 256
ext4fs read 0 group descriptor (blkno 1 blkoff 0)
iterate >.<
ext4fs read 0 group descriptor (blkno 1 blkoff 0)
<DIR>       4096 .
iterate >..<
ext4fs read 0 group descriptor (blkno 1 blkoff 0)
<DIR>       4096 ..
iterate >lost+found<
ext4fs read 0 group descriptor (blkno 1 blkoff 0)
<DIR>      16384 lost+found
iterate >etc<
ext4fs read 832 group descriptor (blkno 7 blkoff 2048)
<DIR>       4096 etc
iterate >media<
ext4fs read 416 group descriptor (blkno 4 blkoff 1024)
<DIR>       4096 media
iterate >var<
ext4fs read 848 group descriptor (blkno 7 blkoff 2560)
<DIR>       4096 var
iterate >usr<
ext4fs read 1760 group descriptor (blkno 14 blkoff 3072)
<DIR>          0 usr
iterate >mnt<
ext4fs read 80 group descriptor (blkno 1 blkoff 2560)
<DIR>       4096 mnt
iterate >dev<
ext4fs read 1152 group descriptor (blkno 10 blkoff 0)
<DIR>          0 dev
iterate >home<
ext4fs read 1472 group descriptor (blkno 12 blkoff 2048)
<DIR>          0 home
iterate >run<
ext4fs read 864 group descriptor (blkno 7 blkoff 3072)
<DIR>       4096 run
iterate >boot<
ext4fs read 224 group descriptor (blkno 2 blkoff 3072)
<DIR>       4096 boot
iterate >tmp<
ext4fs read 1184 group descriptor (blkno 10 blkoff 1024)
<DIR>          0 tmp
iterate >sbin<
ext4fs read 576 group descriptor (blkno 5 blkoff 2048)
<DIR>       4096 sbin
iterate >proc<
ext4fs read 1632 group descriptor (blkno 13 blkoff 3072)
<DIR>          0 proc
iterate >bin<
ext4fs read 1216 group descriptor (blkno 10 blkoff 2048)
<DIR>          0 bin

The problem is in the directories with sizes of 0. It does seem to be
directories with higher blkno's. Perhaps the lack of support for hash
table directory entries is a problem. Just guessing here as I don't know
much about ext4 structure.

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.

Rob

  reply	other threads:[~2012-08-13 18:28 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 [this message]
2012-08-13 19:17               ` Wolfgang Denk
2012-08-13 20:30                 ` Rob Herring
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=50294743.5010907@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