From: Artem Bityutskiy <dedekind1@gmail.com>
To: Steve Iribarne <siribarne@grid-net.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Need to recover from corruption
Date: Thu, 20 Oct 2011 19:23:53 +0300 [thread overview]
Message-ID: <1319127839.20953.10.camel@sauron> (raw)
In-Reply-To: <4E9CA094.4090002@grid-net.com>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Mon, 2011-10-17 at 14:39 -0700, Steve Iribarne wrote:
> On 10/16/2011 04:43 AM, Artem Bityutskiy wrote:
> > On Thu, 2011-10-13 at 13:59 -0700, Steve Iribarne wrote:
> >> I work on a system where we need to be as 100% uptime as possible. The
> >> other day we had an issue here where one of our applications was
> >> crashing while a write to one of the partitions was happening.
> >>
> >> I then turned on UBIFS debugging in u-boot and I have a bunch of info
> >> but I have no idea what is going on.
> > Well, judging from the log UBIFS went nuts for some reason (negative
> > free space). I've never seen this before.
> >
> > Could you please write some more information about your system, flash,
> > kernel version, etc. Please, follow these instructions:
> > http://www.linux-mtd.infradead.org/faq/ubifs.html#L_how_send_bugreport
>
> I'm working on getting this info for you now.
Could you please also verify your flash with the mtd tests. The symptoms
do not look like you have driver-level issues, but this is a good idea
to do anyway. You can find the tests in the kernel and some info at the
MTD web page.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-10-20 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 20:59 Need to recover from corruption Steve Iribarne
2011-10-16 11:43 ` Artem Bityutskiy
2011-10-17 21:39 ` Steve Iribarne
2011-10-20 16:23 ` 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=1319127839.20953.10.camel@sauron \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=siribarne@grid-net.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.