From: Rickard X Andersson <rickaran@axis.com>
To: Zhihao Cheng <chengzhihao1@huawei.com>,
richard@nod.at, linux-mtd@lists.infradead.org
Cc: rickard314.andersson@gmail.com
Subject: Re: Lots of fastmap writes
Date: Fri, 14 Jun 2024 13:42:36 +0200 [thread overview]
Message-ID: <aad1b520-ee9e-476f-911b-45be9eb09195@axis.com> (raw)
In-Reply-To: <f92bb95d-05a1-315b-000c-5189004175d5@huawei.com>
On 6/4/24 03:52, Zhihao Cheng wrote:
> 在 2024/6/4 9:41, Zhihao Cheng 写道:
>> 在 2024/6/3 16:55, Rickard x Andersson 写道:
>>> Hi,
>>>
>>> I have a system running Linux 5.10 which logs quite a lot to a
>>> database. The system has been running OK since before Christmas but
>>> now it usually fails after a few hours with errors like these:
>>>
>>> May 6 22:29:58 172.26.203.90 warning ubi2 warning: ubi_io_read:
>>> error -74 (ECC error) while reading 58 bytes from PEB 1:230872, read
>>> only 58 bytes, retry
>>> May 7 00:11:08 172.26.203.90 warning ubi2 warning: ubi_io_read:
>>> error -74 (ECC error) while reading 58 bytes from PEB 40:239752, read
>>> only 58 bytes, retry
>>> May 7 00:11:08 172.26.203.90 err ubi2 error: ubi_io_read:
>>> error -74 (ECC error) while reading 58 bytes from PEB 40:239752, read
>>> 58 bytes
>>>
>>> Fastmap is used on this system. The ECC errors are usually in the
>>> fastmap area, erase blocks 0- 63.
>>>
>>> When looking more closely at the erase counters they look something
>>> like this:
>>>
>>> 0 - 63: 29600
>>> 64 - 2043: 2200
>>
>> Try this series of patches
>> https://lore.kernel.org/linux-mtd/20230812080005.3162125-2-chengzhihao1@huawei.com/T/
>
> BTW, after applying the patches, the kernel should run on a new flash,
> the improved wear-leveling algorithm cannot rescue the worn out image.
>
Thanks for the patches!
I have backported the patches to Linux kernel 6.1. Do you think the
patches are safe to apply to Linux kernel 6.1?
Another thing, would it not be possible to rescue that particular worn
out device by simply turning fastmap off on that device?
Best regards,
Rickard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-06-14 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 8:55 Lots of fastmap writes Rickard x Andersson
2024-06-04 1:41 ` Zhihao Cheng
2024-06-04 1:52 ` Zhihao Cheng
2024-06-14 11:42 ` Rickard X Andersson [this message]
2024-06-14 12:28 ` Zhihao Cheng
2024-06-17 11:20 ` Rickard x Andersson
2024-06-17 13:21 ` Zhihao Cheng
2024-06-17 13:48 ` Rickard x Andersson
2024-06-17 13:55 ` Zhihao Cheng
2024-06-04 6:47 ` Richard Weinberger
2024-06-14 11:45 ` Rickard X Andersson
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=aad1b520-ee9e-476f-911b-45be9eb09195@axis.com \
--to=rickaran@axis.com \
--cc=chengzhihao1@huawei.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=rickard314.andersson@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