From: Woody Wu <narkewoody@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Block numbers of BEB
Date: Sun, 05 Oct 2014 22:49:08 +0700 [thread overview]
Message-ID: <db3c3c22-b896-4b73-bece-99a1db7d602a@email.android.com> (raw)
In-Reply-To: <CAFLxGvxm7RU-_5r658pA2C5EJ6NGGX2sfErNB9Hosq98QP8G2A@mail.gmail.com>
What I said of checking /proc is wrong. What I indeed checked was /sys/class/ubi as you mentioned. The problem is, under the /sys/class/ubi, there is no information about what blocks are marked as bad, there is only information about the total number of bad blocks.
On October 5, 2014 10:41:50 PM GMT+07:00, Richard Weinberger <richard.weinberger@gmail.com> wrote:
>On Sun, Oct 5, 2014 at 8:04 AM, Woody Wu <narkewoody@gmail.com> wrote:
>> Hi,
>>
>> I can see how many bad erase blocks it had developed from the /proc
>directory, but where can I get know what block numbers these bad blocks
>on?
>>
>> Any hint from you will be appreciated.
>
>In case you're using UBI please see /sys/class/ubi/ubi0/
--
sent from mobile
next prev parent reply other threads:[~2014-10-05 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 6:04 Block numbers of BEB Woody Wu
2014-10-05 15:41 ` Richard Weinberger
2014-10-05 15:49 ` Woody Wu [this message]
2014-10-05 15:53 ` Richard Weinberger
2014-10-05 15:58 ` Woody Wu
2014-10-05 16:00 ` Richard Weinberger
2014-10-05 16:17 ` Woody Wu
2014-10-05 16:21 ` Richard Weinberger
2014-10-05 16:40 ` Woody Wu
2014-10-06 7:53 ` Ricard Wanderlof
2014-10-06 8:41 ` Woody Wu
2014-10-06 8:59 ` Ricard Wanderlof
2014-10-06 11:25 ` Woody Wu
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=db3c3c22-b896-4b73-bece-99a1db7d602a@email.android.com \
--to=narkewoody@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