From: Richard Weinberger <richard.weinberger@gmail.com>
To: Kiran B S <bs.kiran81@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Seeing ubifs unmap LEB error with linux 2.6.35 kernel
Date: Fri, 17 Jan 2020 01:19:44 +0100 [thread overview]
Message-ID: <CAFLxGvxJQws9qMY51Wd+buJirYUR=mSBUO-MurAMOPP3MG2pyQ@mail.gmail.com> (raw)
In-Reply-To: <CA+VTqBmNiHQkaOS3aApekiuP8XOrUB8gf39EYAA=AfGpiTDRiA@mail.gmail.com>
On Thu, Jan 9, 2020 at 9:37 AM Kiran B S <bs.kiran81@gmail.com> wrote:
>> On Tue, Jan 7, 2020 at 6:01 PM Kiran B S <bs.kiran81@gmail.com> wrote:
>>>
>>> Hi Richard,
>>> We could hit this error now on multiple systems. An attempt to write some data was done during this time.
>>> Please find below the stack dump trace as per the changes that you had suggested:
>>>
>>> Stack dump trace:
>>> [dump_backtrace_entry]:59:[<c04ca258>] (unwind_backtrace+0x0/0xe8) from [<c0663280>] (ubi_leb_unmap+0x68/0x70)
>>> [dump_backtrace_entry]:59:[<c0663280>] (ubi_leb_unmap+0x68/0x70) from [<c05d0088>] (ubifs_garbage_collect+0x2f4/0x308)
>>> [dump_backtrace_entry]:59:[<c05d0088>] (ubifs_garbage_collect+0x2f4/0x308) from [<c05bcaf4>] (make_reservation+0xec/0x3a0)
>>> [dump_backtrace_entry]:59:[<c05bcaf4>] (make_reservation+0xec/0x3a0) from [<c05bd718>] (ubifs_jnl_write_data+0xec/0x1b8)
>>> [dump_backtrace_entry]:59:[<c05bd718>] (ubifs_jnl_write_data+0xec/0x1b8) from [<c05be8d8>] (do_writepage+0x100/0x16c)
So we know now that garbage collection tries to unmap an invalid LEB.
Like I said before, your kernel is super old and unsupported.
You can try try to backport fixes which affect garbage collection in UBIFS.
But I'd strongly suggest to upgrade the kernel.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-01-17 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Seeing ubifs unmap LEB error with linux 2.6.35 kernel 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 [this message]
2019-10-17 17:38 Kiran Bangalore Sathyanarayana (kibangal)
2019-10-17 20:44 ` 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='CAFLxGvxJQws9qMY51Wd+buJirYUR=mSBUO-MurAMOPP3MG2pyQ@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=bs.kiran81@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).