linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Bhuvanchandra DV <bhuvanchandradv@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Bhuvanchandra DV <bhuvanchandradv@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS errors when file-system is full
Date: Tue, 14 Jul 2015 09:53:03 +0530	[thread overview]
Message-ID: <55A48EA7.6050302@gmail.com> (raw)
In-Reply-To: <CAFLxGvzriSX-aGh_NShqP7McyZQK6bOdnOm=yXkZSUfX=r8pzw@mail.gmail.com>

Hello Richard,

On 07/13/2015 07:39 PM, Richard Weinberger wrote:

> On Mon, Jul 13, 2015 at 3:55 PM, Bhuvanchandra DV
> <bhuvanchandradv@gmail.com> wrote:
>> Hello,
>>
>> Facing some issues with UBIFS mounting when NAND flash is almost near to
>> full.
>>
>> Hardware:
>> SOC: Freescale Vybrid
>> COM: Colibri VF50
>> Flash: Macronic NAND 128MB, 3.3V, 8-Bit
>>
>> By default the Linux Image flashed on the NAND flash almost occupies ~93% of
>> the flash.
>> Observed this issue when power resetting the module for about 500 times,
>> with journalctl
>> enabled, after around 500 power cycles the debug log fills up the nand
>> flash. When the
>> flash menory is about to full, the ubifs partation is un-mountable.
>>
>> The nand flash controller driver is under review and passed all MTD tests.
>> https://lkml.org/lkml/2015/6/18/847
>>
>>
>> Debug log during UBIFS mounting from U-Boot:
>>
>> U-Boot 2015.04 (May 18 2015 - 15:37:34)
>>
>> CPU: Freescale Vybrid VF500 at 396 MHz
>> Reset cause: POWER ON RESET
>> DRAM:  128 MiB
>> NAND:  128 MiB
>> MMC:   FSL_SDHC: 0
>> *** Warning - bad CRC, using default environment
>>
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Model: Toradex Colibri VF50 128MB V1.1A, Serial# 04815679
>> Net:   FEC
>> Hit any key to stop autoboot:  0
>> Booting from NAND...
>> UBI: default fastmap pool size: 50
>> UBI: default fastmap WL pool size: 25
>> UBI: attaching mtd1 to ubi0
>> UBI: attached by fastmap
> Is this a recent kernel with all fastmap fixes applied?

I'm sorry! I didn't mention about the kernel version before.

Tested with 4.0.5 kernel[1]. I think your fastmap fixes[2] are not available with
this kernel version.

Lately also tested on 4.1.1 kernel[3], observed the same issues.

[1]http://git.toradex.com/cgit/linux-toradex.git/log/?h=toradex_vf_4.0
[2]http://lists.infradead.org/pipermail/linux-mtd/2015-April/058747.html
[3]http://git.toradex.com/cgit/linux-toradex.git/log/?h=toradex_vf_4.1-next

>
>
Best regards,
Bhuvan

  reply	other threads:[~2015-07-14  4:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 13:55 UBIFS errors when file-system is full Bhuvanchandra DV
2015-07-13 14:09 ` Richard Weinberger
2015-07-14  4:23   ` Bhuvanchandra DV [this message]
2015-07-14  6:13     ` Richard Weinberger
2015-07-14  6:30       ` Bhuvanchandra DV
2015-07-14  6:32         ` Richard Weinberger
2015-07-14  8:29           ` Bhuvanchandra DV
2015-07-14  8:42             ` Richard Weinberger
2015-07-14 10:08               ` Bhuvanchandra DV
2015-07-14 11:06                 ` Richard Weinberger
     [not found]                   ` <55A74812.2020906@gmail.com>
     [not found]                     ` <55A74AA1.2000000@nod.at>
     [not found]                       ` <55A7540C.3050900@nod.at>
     [not found]                         ` <55A7592D.6010906@gmail.com>
     [not found]                           ` <55A75A05.7040603@nod.at>
2015-07-16  7:33                             ` Bhuvanchandra DV
2015-07-21  6:04                             ` Bhuvanchandra DV
2015-07-21  6:14                               ` Richard Weinberger
2015-07-22  7:10                                 ` Bhuvanchandra DV
2015-07-22  7:20                                   ` Richard Weinberger
2015-07-24 14:43                                     ` Bhuvanchandra DV
2015-07-24 16:51                                       ` Richard Weinberger
2015-07-31 16:47                                         ` Bhuvanchandra DV
2015-08-01  6:36                                           ` Richard Weinberger
2015-08-06 10:31                                             ` Bhuvanchandra DV
2015-08-07 12:37                                               ` Richard Weinberger
2015-08-12  7:01                                                 ` Stefan Agner
2015-08-12  7:27                                                   ` Richard Weinberger
2015-09-01  0:45                                                     ` Stefan Agner
2015-09-01  1:43                                                       ` Brian Norris
2015-09-01  2:20                                                         ` Stefan Agner
2015-09-02 19:58                                                         ` Stefan Agner
2015-09-02 20:13                                                           ` Brian Norris
2015-09-02 20:41                                                             ` Stefan Agner
2015-09-07 13:47                                                           ` Bhuvanchandra
2015-09-11  4:03                                           ` Bhuvanchandra
2015-09-12  9:39                                             ` Richard Weinberger
2015-09-13  4:45                                               ` Bhuvanchandra
2015-07-16  7:35                     ` Fwd: " Bhuvanchandra DV

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=55A48EA7.6050302@gmail.com \
    --to=bhuvanchandradv@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.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).