public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V5 1/2] ext4fs ls load support
Date: Wed, 12 Sep 2012 15:49:46 -0700	[thread overview]
Message-ID: <20120912224946.GA5852@bill-the-cat> (raw)
In-Reply-To: <50294743.5010907@gmail.com>

On Mon, Aug 13, 2012 at 01:28:19PM -0500, Rob Herring wrote:
> 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:
[snip]
> 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.

I took an Ubuntu install I had (for x86) that was on a USB drive, had
been pretty extensively used, and was is ext4.  I couldn't find any size
0 directories.  Are you able to reproduce this problem on other
hardware?  Is the image in question NOT remountable as ext3 (extents is
set, generated) ?  My biggest concern is breakage among ext2/3
filesystems.  Thanks!

-- 
Tom

  parent reply	other threads:[~2012-09-12 22:49 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
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 [this message]
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=20120912224946.GA5852@bill-the-cat \
    --to=trini@ti.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