kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bad block Management Patch
Date: Tue, 24 Jan 2017 08:38:13 +0100	[thread overview]
Message-ID: <20170124073813.GA31455@kroah.com> (raw)
In-Reply-To: <8c362ab6c4194debb9dcced1714cb368@SGPMBX1023.APAC.bosch.com>

On Tue, Jan 24, 2017 at 07:15:33AM +0000, Anurag Raghavan (RBEI/ETW11) wrote:
> Hi Greg,
> 
> Thank You for the information. I have few more concerns here,
> 
> I am facing the following uncorrectable ECC error, Can you suggest any kernel version or any patches to overcome this issue.
> 
> 
> Error logs:
> 
> [    1.797141] UBI error: ubi_io_read: error -74 (ECC error) while reading 253952 bytes from PEB 445:8192, read 253952 bytes
> [    1.808274] UBIFS error (pid 491): ubifs_scan: corrupt empty space at LEB 489:233760
> [    1.816037] UBIFS error (pid 491): ubifs_scanned_corruption: corruption at LEB 489:233760
> [    1.828660] UBIFS error (pid 491): ubifs_scan: LEB 489 scanning failed
> [    1.835215] UBIFS warning (pid 491): ubifs_ro_mode: switched to read-only mode, error -117
> [    1.843502] UBIFS error (pid 491): make_reservation: cannot reserve 58 bytes in jhead 2, error -117
> [    1.852569] UBIFS error (pid 491): do_writepage: cannot write page 0 of inode 76584, error -117
> dpkg: error: unable to sync new file '/var/lib/dpkg/arch-new': Structure needs cleaning

Are you sure your hardware isn't breaking down?

Also, can you try the 4.9 kernel tree?  Lots of ubifs changes have
happened since 3.0 was released, over 5 years ago...

thanks,

greg k-h

      reply	other threads:[~2017-01-24  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24  7:02 Bad block Management Patch Anurag Raghavan (RBEI/ETW11)
2017-01-24  7:09 ` Greg KH
2017-01-24  7:15   ` Anurag Raghavan (RBEI/ETW11)
2017-01-24  7:38     ` Greg KH [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=20170124073813.GA31455@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).