From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mark <xiaoming1981.zhang@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>, zxm927@163.com
Subject: Re: Why the nand chip driver "should never return -EBADMSG if it failed to read all the request data"
Date: Sun, 22 Apr 2012 17:37:01 +0300 [thread overview]
Message-ID: <1335105421.28267.21.camel@brekeke> (raw)
In-Reply-To: <4F8AD1E5.6080307@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Sun, 2012-04-15 at 21:49 +0800, Mark wrote:
> And, after I patched the nand driver, in most of the situations the
> UBIFS can be successfully recovered, but I still get this error:
>
> ...
> UBI error: ubi_io_read: error -77 while reading 126976 bytes from PEB
> 2:4096, read 126976 bytes
> UBIFS error (pid 481): insert_node: duplicate sqnum in replay
> mount: mounting ubi13_0 on /usr/local/hmt/appdata failed: Invalid argument
> ...
>
> Does this mean this should never happen to UBIFS? Then what could be the
> reason?
> Thank you very much, and my test environment:
I see ubi_dbg_dump_stack() call in ubi_io_read() when it returns an
error. If you have debugging enabled - you should have the dump in your
kernel buffer.
Yeah, we should turn it into 'dump_stack()' to always have the dump. I'd
gratefully accept a patch.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-04-22 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 13:49 Why the nand chip driver "should never return -EBADMSG if it failed to read all the request data" Mark
2012-04-22 14:37 ` Artem Bityutskiy [this message]
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=1335105421.28267.21.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=xiaoming1981.zhang@gmail.com \
--cc=zxm927@163.com \
/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