From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 12 Sep 2012 15:49:46 -0700 Subject: [U-Boot] [PATCH V5 1/2] ext4fs ls load support In-Reply-To: <50294743.5010907@gmail.com> References: <1326131690-25090-1-git-send-email-uma.shankar@samsung.com> <1337961104-21198-1-git-send-email-uma.shankar@samsung.com> <20120809215028.B6F0E20401A@gemini.denx.de> <50244D5A.3080304@gmail.com> <20120813115226.A59C9204046@gemini.denx.de> <50294743.5010907@gmail.com> Message-ID: <20120912224946.GA5852@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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