From: Joe Buehler <aspam@cox.net>
To: u-boot@lists.denx.de
Subject: ext2ls zero-length directory entries?
Date: Tue, 25 Aug 2020 16:08:35 -0400 [thread overview]
Message-ID: <5F456FC3.8000904@cox.net> (raw)
(This is a vendor-modified version of uboot 2011.03.)
I am running into problems using ext2load, the command complains that
the file of interest is not found. I know it's there though since it is
fine under LINUX.
Doing some poking around, I see that ext2ls is showing mostly zero
length on the subdirs I am interested in loading files from -- thus the
"not found" issues. Some of the directories have enormous lengths and
crash uboot when attempting to list their content.
I am attempting to load from a large SATA disk partitioned into two
equal-size partitions that add up to the whole disk. No problems with
the first partition, the second partition has the issue.
Does this ring a bell with anyone? Perhaps it is a disk size issue and
an old uboot? LINUX says the following about the disk:
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata1.00: supports DRM functions and may not be fully accessable.
ata1.00: ATA-10: Micron_1100_MTFDDAK256TBN, M0MU031, max UDMA/133
ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: supports DRM functions and may not be fully accessable.
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access ATA Micron_1100_MTFD n/a PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
Joe Buehler
reply other threads:[~2020-08-25 20:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5F456FC3.8000904@cox.net \
--to=aspam@cox.net \
--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