From: Iwo Mergler <iwo@call-direct.com.au>
To: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Looks like a UBIFS bug...
Date: Thu, 03 Dec 2009 15:22:03 +1100 [thread overview]
Message-ID: <4B173CEB.5050103@call-direct.com.au> (raw)
Hi all,
I've got some weird UBIFS-related behaviour. I'd welcome
any suggestions.
This is an ARM927-based embedded system with NAND FLASH,
Kernel 2.6.32-rc8 with a custom MTD NAND driver.
While attempting to write a file to a UBIFS volume, UBIFS claims
UBIFS error (pid 866): check_lpt_type: invalid type (15) in LPT node type 0
followed by "cannot reserve n bytes" messages every second or so.
After this point the fs is read-only.
I don't know how to trigger it reliably, but while experimenting
with different mtd partition sizes and debug levels, I was able
to catch it with debug level 2 enabled. The full log is attached.
I tried to cut the problem down, disabling unrelated volumes and
reducing the MTD partition size, but in that configuration I was
not able to trigger the problem with UBIFS debug enabled. That is,
enabling debug made the problem go away.
Thus, the log shows two UBIFS partitions. /opt is the one with
the problem:
ubi0:usrl 65.2M 20.0k 61.8M 0% /usr/local
ubi1:opt 109.0M 1.6M 102.6M 2% /opt
Basically, starting from a fully erased MTD partition, I run
ubiattach /dev/ubi_ctrl -m 6
ubimkvol /dev/ubi1 -N opt -m
mount -t ubifs ubi1:opt /opt
After that I get the system to write a file into /opt. This is
data streamed over Ethernet, so write units are probably odd sized
blocks. I don't know if this is significant, but I wasn't able
to trigger the problem any other way (e.g. dd if=/dev/urandom, or
copying the exact same file via cp).
Kind regards,
Iwo
next reply other threads:[~2009-12-03 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 4:22 Iwo Mergler [this message]
2009-12-03 4:34 ` Looks like a UBIFS bug Iwo Mergler
2009-12-03 6:04 ` Looks like a UBIFS bug... - Solved Iwo Mergler
2009-12-03 7:33 ` Artem Bityutskiy
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=4B173CEB.5050103@call-direct.com.au \
--to=iwo@call-direct.com.au \
--cc=linux-mtd@lists.infradead.org \
/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