linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Reginald Perrin <reggyperrin@yahoo.com>
Cc: MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS Corruption
Date: Mon, 18 Jul 2011 14:38:05 +0300	[thread overview]
Message-ID: <1310989090.20738.46.camel@sauron> (raw)
In-Reply-To: <1310130765.68852.YahooMailRC@web114617.mail.gq1.yahoo.com>

On Fri, 2011-07-08 at 06:12 -0700, Reginald Perrin wrote:
> Hi folks,
> 
> We're using ubifs in an embedded uclinux system (based on ADI Blackfin's BF524). 
>  Been working great for us for a while.  Kernel is 2.6.34.7 (uclinux).
> 
> However, we just saw 2 corruptions within the past 48h that we can't explain. 
>  We've been doing the same basic operation (in terms of flashing/reading/writing 
> images) for quite some time, and have reflashed our units many times (over 
> thousands of different hardware units).
> 
> Device #1 failure:
> * Device was running out of a partition mounted to /home (a 93MB partition from 
> a 128MB NAND device)
> * Our app was running normally and locked up (not sure why).  Our code may have 
> been updating a sqlite database located in that partition
> * When we power cycled, the partition had the corruption issue noted.
> 
> Device #1 boot log:
> UBI device number 1, total 750 LEBs (96768000 bytes, 92.3 MiB), available 0 LEBs 
> (0 bytes), LEB size 129024 bytes (126.0 KiB) 
> [ 5.228000] UBIFS: recovery needed 
> [ 5.320000] UBIFS error (pid 363): ubifs_scanned_corruption: corruption at LEB 
> 172:45056 
> [ 5.348000] UBIFS error (pid 363): ubifs_recover_leb: LEB 172 scanning failed 
> mount: mounting ubi1:home on /home failed: Structure needs cleaning 

While this is very typical symptom which might mean many things,

> Device #2 failure:
> * Device was running normally.
> * We upgraded our application (which involved updating executables on that 
> partition)
> * After the successful upgrade, we powered the unit down and stored 
> * Days later, powered up the device and the above invalid CRC as noted
> 
> Device #2 boot log:
> UBI device number 1, total 750 LEBs (96768000 bytes, 92.3 MiB), available 0 LEBs 
> (0 bytes), LEB size 129024 bytes (126.0 KiB) 
> [ 5.488000] UBIFS: recovery needed 
> [ 5.492000] UBIFS error (pid 365): check_lpt_crc: invalid crc in LPT node: crc 
> a0 calc 9013
> mount: mounting ubi1:home on /home failed: Invalid argument

I do not remember this one. This may be an UBIFS bug of course, but
quite possible this is just flash corruption or memory corruption (e.g.,
some driver corrupts memory and makes UBIFS write incorrect information
to the flash).

-- 
Best Regards,
Artem Bityutskiy

      parent reply	other threads:[~2011-07-18 11:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 13:12 UBIFS Corruption Reginald Perrin
2011-07-18 11:33 ` Artem Bityutskiy
2011-07-19 20:47   ` Reginald Perrin
2011-07-26 19:17   ` Reginald Perrin
2011-08-02 16:14     ` Reginald Perrin
2011-08-15 12:30       ` Artem Bityutskiy
2011-08-15 12:29     ` Artem Bityutskiy
2011-11-28 20:04       ` Reginald Perrin
2011-11-29 22:30         ` Artem Bityutskiy
2011-12-07 17:19         ` Reginald Perrin
2011-12-08 21:42           ` Artem Bityutskiy
2011-12-12 14:29             ` Reginald Perrin
2011-12-12 16:34               ` Artem Bityutskiy
     [not found]                 ` <1323709988.3066.YahooMailNeo@web114618.mail.gq1.yahoo.com>
2011-12-13 16:25                   ` Reginald Perrin
2011-12-13 20:19                     ` Artem Bityutskiy
2011-07-18 11:38 ` 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=1310989090.20738.46.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=reggyperrin@yahoo.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;
as well as URLs for NNTP newsgroup(s).