From: Artem Bityutskiy <dedekind1@gmail.com>
To: Timon ter Braak <timonterbraak@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach error!
Date: Mon, 23 May 2011 15:42:55 +0300 [thread overview]
Message-ID: <1306154575.2785.15.camel@localhost> (raw)
In-Reply-To: <loom.20110520T181331-434@post.gmane.org>
On Fri, 2011-05-20 at 16:24 +0000, Timon ter Braak wrote:
> I will be happy to provide more information, but I am not sure what
> exactly. It is difficult to separate what procedure corrupt the filesystem
> and what does work. For example, even a normal 'reboot' command
> results in the message 'recovery needed'; is that normal?
Start with this:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_how_send_bugreport
If you cannot isolate the error - I cannot do it as well for sure. So
please, try to fine one specific thing which you think is a problem, and
ask to help with that specific thing. The above link should help. In
general, the first things you need to do are:
1. validate your mtd device with the test - this is always good thing to
do.
2. enable UBIFS debugging (not debugging messages)
3. report the issue properly as it is described at the MTD web site.
WRT. reboot: if your 'reboot' command results in 'recovery needed' then
your 'reboot' command does not unmount the file-system and just reboots
it. Of course from UBIFS's POW this is a power cut and it needs
recovery. But there is nothing to be afraid of if you know you synced
your files. So you need to take a look what "reboot" does - it may do
completely different things on different systems. E.g., does it sync the
data? does it unmount FSes?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-05-23 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:26 ubiattach error! jerry
2010-04-08 8:23 ` Artem Bityutskiy
2011-05-20 14:14 ` Timon ter Braak
2011-05-20 14:23 ` Artem Bityutskiy
2011-05-20 16:24 ` Timon ter Braak
2011-05-23 12:42 ` 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=1306154575.2785.15.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=timonterbraak@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.