From: Russell Zuck <rzuck@cincinnatitechnologies.com>
To: linux-mtd@lists.infradead.org
Subject: Re: UBIFS corruption after software upgrade
Date: Wed, 01 Aug 2012 08:40:09 -0400 [thread overview]
Message-ID: <501923A9.7030002@cincinnatitechnologies.com> (raw)
In-Reply-To: <500F0D81.8050902@cincinnatitechnologies.com>
On 7/24/2012 5:02 PM, Russell Zuck wrote:
> I have not yet attempted to reproduce this issue using nandsim nor do I
> have a simple reproducer for the problem yet. Please provide some ideas
> about how to simulate the reboot using nandsim as I think the reboot
> portion of this scenario will be critical to reproducing the issue.
Can anyone direct me to some information that might help me simulate a
reboot using nandsim to attempt to reproduce my UBIFS corruption issue?
Additionally, I would really appreciate any suggestions, tips, tricks,
criticisms of the upgrade process I outlined previously, or "Have you
considered this" type questions. I've read everything I could find that
even remotely pertains to my scenario but nothing is clicking for me
yet. I'm desperately trying to resolve my issue. Any guidance would be
welcome.
Best regards,
Russ
next prev parent reply other threads:[~2012-08-01 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 21:02 UBIFS corruption after software upgrade Russell Zuck
2012-08-01 12:40 ` Russell Zuck [this message]
2012-08-02 2:10 ` Subodh Nijsure
2012-08-22 13:18 ` Artem Bityutskiy
2012-08-24 17:55 ` Russell Zuck
2012-08-27 16:17 ` Russell Zuck
2012-08-31 11:21 ` Artem Bityutskiy
2012-08-22 13:21 ` Artem Bityutskiy
2012-08-22 13:02 ` Artem Bityutskiy
2012-08-31 11:30 ` 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=501923A9.7030002@cincinnatitechnologies.com \
--to=rzuck@cincinnatitechnologies.com \
--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;
as well as URLs for NNTP newsgroup(s).