public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Thang Dao Duy <hanbaoquansexy@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Confuse with WL_THRESHOLD
Date: Sun, 07 Jun 2009 13:23:00 +0300	[thread overview]
Message-ID: <1244370180.5847.322.camel@localhost.localdomain> (raw)
In-Reply-To: <a1fb7300906051703p148c5d1k7fd46257c8031ac6@mail.gmail.com>

On Sat, 2009-06-06 at 07:03 +0700, Thang Dao Duy wrote:
> Hi everyone.
> I used NANDsim and ubifs not for along time. Now, I have confused with
> wear-leveling threshold. If i give parameter WL_THRESHOLD in Kernel is
> small (example, the value is  3), then when i write a file size 2 MiB
> to NAND about 200 times, it makes me cannot read EC and VID headers of
> one PEB (example PEB 10). May be that PEB is bad ? And when i set the
> WL_THRESHOLD is higher (the value is 20), i write a file 2MiB about
> 1000 times, nothing 's happen, i can read headers of any PEB. So can
> you tell me what make this happen, and show me where in ubi source in
> kernel.

Looks like a bug. Please, describe precisely how to reproduce it,
and I'll take a look at this.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-06-07 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a1fb7300906022244g5cd882acw7de4b9b0ecc35547@mail.gmail.com>
2009-06-06  0:03 ` Confuse with WL_THRESHOLD Thang Dao Duy
2009-06-07 10:23   ` Artem Bityutskiy [this message]
2009-06-08  7:26     ` Artem Bityutskiy
2009-06-10  3:31       ` Thang Dao Duy

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=1244370180.5847.322.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=hanbaoquansexy@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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