linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Kiran Bangalore Sathyanarayana (kibangal)" <kibangal@cisco.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: "Sriranjan Bose \(srbose\)" <srbose@cisco.com>
Subject: Seeing ubifs unmap LEB error with linux 2.6.35 kernel
Date: Thu, 17 Oct 2019 17:38:15 +0000	[thread overview]
Message-ID: <BYAPR11MB2566C2E89585B6F7AD7F083DC56D0@BYAPR11MB2566.namprd11.prod.outlook.com> (raw)

Hi,
We are seeing the below ubifs errors with linux 2.6.35 Kernel:

3:2019 Jul 21 13:13:03 UTC:4.0(2h):kernel:-:<3>UBIFS error (pid 24831): ubifs_leb_unmap: unmap LEB -1 failed, error -22
4:2019 Jul 21 13:13:03 UTC:4.0(2h):kernel:-:<4>UBIFS warning (pid 24831): ubifs_ro_mode: switched to read-only mode, error -22
3:2019 Jul 21 13:13:03 UTC:4.0(2h):kernel:-:<3>UBIFS error (pid 24831): make_reservation: cannot reserve 4144 bytes in jhead 2, error -22
3:2019 Jul 21 13:13:03 UTC:4.0(2h):kernel:-:<3>UBIFS error (pid 24831): do_writepage: cannot write page 98 of inode 67, error -22
3:2019 Jul 21 13:13:03 UTC:4.0(2h):kernel:-:<3>UBIFS error (pid 24581): make_reservation: cannot reserve 4144 bytes in jhead 2, error -30
3:2019 Jul 21 13:13:03 UTC:4.0(2h):kernel:-:<3>UBIFS error (pid 24581): do_writepage: cannot write page 99 of inode 67, error -30
3:2019 Jul 21 13:13:03 UTC:4.0(2h):kernel:-:<3>Buffer I/O error on device loop2, logical block 1

The system has a NAND flash with ubifs filesystem installed. The above errors happened randomly at runtime and ubifs switched to read-only mode.
The NAND flash itself is fine and there are no badblocks detected.
"ubinfo -a" output is as below:
UBI version:                    1
Count of UBI devices:           1
UBI control device major/minor: 10:63
Present UBI devices:            ubi0

ubi0:
Volumes count:                           1
Logical eraseblock size:                 126976
Total amount of logical eraseblocks:     1024 (130023424 bytes, 124.0 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  10
Current maximum erase counter value:     536
Minimum input/output unit size:          2048 bytes
Character device major/minor:            235:0
Cisco UBI Flash Worn:                    No
Present volumes:                         0

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        1010 LEBs (128245760 bytes, 122.3 MiB)
State:       OK
Name:        data
Character device major/minor: 235:1

This has occurred on multiple systems now.
Can you please provide me more info on this error? Is this any known issue with linux 2.6.35 Kernel?
Please let me know how to proceed with fixing this(any specific patch that needs to be specifically applied on 2.6.35 kernel).

Regards,
Kiran.



______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2019-10-17 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 17:38 Kiran Bangalore Sathyanarayana (kibangal) [this message]
2019-10-17 20:44 ` Seeing ubifs unmap LEB error with linux 2.6.35 kernel Richard Weinberger
     [not found] <CA+VTqBkr+1Kd0QSLUJbRZG3CMZdNct_svGNjSfVh=8Gaozfrfw@mail.gmail.com>
     [not found] ` <CA+VTqB=0QSWG68GLO=6LuetoSwwiuxDT6k_n=m+ruZpbjuvgeQ@mail.gmail.com>
2019-10-19  9:09   ` Richard Weinberger
     [not found]     ` <CA+VTqBnmjXDtz2DdaaM=9-GHBVfYU909qw2V9G8DkYfu3w6DMw@mail.gmail.com>
     [not found]       ` <CA+VTqB=DByeW-NmHoGuybPB1odL+WkwxRg2z4O+qVobHaHpVsA@mail.gmail.com>
     [not found]         ` <CA+VTqBmNiHQkaOS3aApekiuP8XOrUB8gf39EYAA=AfGpiTDRiA@mail.gmail.com>
2020-01-17  0:19           ` Richard Weinberger

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=BYAPR11MB2566C2E89585B6F7AD7F083DC56D0@BYAPR11MB2566.namprd11.prod.outlook.com \
    --to=kibangal@cisco.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=srbose@cisco.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).