From: Akshay Bhat <abhat@lutron.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
hujianyang <hujianyang@huawei.com>
Subject: Re: UBIFS Panic
Date: Thu, 10 Jul 2014 17:38:44 -0400 [thread overview]
Message-ID: <53BF07E4.4010302@lutron.com> (raw)
In-Reply-To: <53B2CC06.3000205@nod.at>
On Tue 01 Jul 2014 10:56:06 AM EDT, Richard Weinberger wrote:
> Am 01.07.2014 16:46, schrieb Akshay Bhat:
>>
>>
>> On Tue 01 Jul 2014 10:32:34 AM EDT, Richard Weinberger wrote:
>>> Am 01.07.2014 16:18, schrieb Akshay Bhat:
>>>>
>>>>
>>>> On Tue 01 Jul 2014 03:48:54 AM EDT, Richard Weinberger wrote:
>>>>> Am 01.07.2014 03:09, schrieb hujianyang:
>>>>>>>
>>>>>>> Is enabling UBI_FASTMAP the cause for the panic? If so I can disabled the
>>>>>>> feature and re-test. Do you see any compatibility issue going from:
>>>>>>> Current config -> New config -> Failsafe config
>>>>>>>
>>>>>>
>>>>>> I don't know. But I found func ubi_wl_get_peb() in drivers/mtd/ubi/wl.c
>>>>>> will return an error ENOSPC without any error messages. And this func
>>>>>> seems related with fastmap feature.
>>>>>
>>>>> I have sort of an idea what could going on.
>>>>> Akshay, can you please confirm that you face the issue only with UBI_FASTMAP=y?
>>>>
>>>> I have not been able to recreate the issue with UBI_FASTMAP=n
>>>
>>> Okay, you test case basically fills the filesystem over and over?
>>> And after some time you face the said issue.
>>> Is this correct?
>>
>> Yes. From testing, the "some time" is typically after crossing the WL threshold.
>
> Good. I'll dig into that by the end of the week.
Hi Richard, wanted to check if you got a chance to dig into this?
Thanks.
> Thanks,
> //richard
>
next prev parent reply other threads:[~2014-07-10 21:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 20:28 UBIFS Panic Akshay Bhat
2014-06-27 2:36 ` hujianyang
2014-06-30 13:01 ` Akshay Bhat
2014-06-30 14:48 ` Richard Weinberger
2014-06-30 17:23 ` Akshay Bhat
2014-06-30 17:34 ` Richard Weinberger
2014-07-01 1:09 ` hujianyang
2014-07-01 7:48 ` Richard Weinberger
2014-07-01 14:18 ` Akshay Bhat
2014-07-01 14:32 ` Richard Weinberger
2014-07-01 14:46 ` Akshay Bhat
2014-07-01 14:56 ` Richard Weinberger
2014-07-10 21:38 ` Akshay Bhat [this message]
2014-07-10 21:42 ` Richard Weinberger
2014-07-11 20:45 ` Richard Weinberger
2014-07-16 17:31 ` Akshay Bhat
2014-07-16 21:00 ` Richard Weinberger
2014-07-22 18:39 ` Akshay Bhat
2014-07-01 0:58 ` hujianyang
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=53BF07E4.4010302@lutron.com \
--to=abhat@lutron.com \
--cc=hujianyang@huawei.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 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.