From: Bhuvanchandra DV <bhuvanchandradv@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS errors when file-system is full
Date: Thu, 6 Aug 2015 12:31:58 +0200 [thread overview]
Message-ID: <55C3379E.50000@gmail.com> (raw)
In-Reply-To: <55BC68D6.2070008@nod.at>
Hi Richard,
On 08/01/2015 08:36 AM, Richard Weinberger wrote:
> Am 31.07.2015 um 18:47 schrieb Bhuvanchandra DV:
>> On 07/24/2015 06:51 PM, Richard Weinberger wrote:
>>
>>> Hi!
>>>
>>> Am 24.07.2015 um 16:43 schrieb Bhuvanchandra DV:
>>>> Disabled fastmap in U-Boot, still the corruption is persistent when using
>>>> U-Boot to mount rootfs and load kernel.
>>> Can you please describe your boot setup in detail?
>>> Why does U-Boot _mount_ an UBIFS? Install the kernel on an UBI static volume.
>> U-Boot mounts UBIFS for loading the kernel and device tree blobs availabel in rootfs.
>> Since approximately around ~3-5 % of spare blocks are reserverd for wear leveling
>> (according to the NAND manufacturer). Initially we had a separate UBI partition of 8MB
>> for Kenrel, but after few times of re-writing the kernel to that volume kernel fails
>> with no available free space. Due to that reason we made a single big ubi volume and
>> moved the kernel and device tree blobs to rootfs.
> UBI partition? You mean UBI volume?
Sorry, UBI volume.
> Just install kernel, initrd and dtb on UBI static volumes.
>
> If U-Boot has to mount UBIFS it has to do that in RW mode.
> So, no fastmap for you.
Okay
>> Seems the mtd-utils are not really cross-compile friendly, some how managed to build the ubi-tests
>> tweeking the Makefiles.
> Seeing forward to receive patches or at least a bug report.
Sure will do it.
>
>> The tests ran on ubi partition after isolating it from U-Boot completly.
>> Formatted the ubi partition and then boot with SD card (4.1.2 kernel fastmap enabled/disabled, fm_debug enabled).
>> Please find the below log of ubi-tests:
>>
>> [io_paral] write_thread():222: written and read data are different
> *blink*
Tried to run the io_paral test multiple times seperately with few debug prints added to see what exact
differences with read and write buffers, so far we could see one complete page is read twice even though
it is written once. I'm now confused is the issue happen while reading or while writing. Can you give us
some pointers so that we can narrow down the cause for this failure.
>
> Thanks,
> //richard
Best regards,
Bhuvan
next prev parent reply other threads:[~2015-08-06 10:32 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
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 [this message]
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=55C3379E.50000@gmail.com \
--to=bhuvanchandradv@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 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.