Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Matthias Auchmann <m.auchmann@artech.at>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI/UBIFS on NAND with PEB 4MB
Date: Wed, 14 Dec 2016 08:43:03 +0100	[thread overview]
Message-ID: <20161214084303.0059cbf5@bbrezillon> (raw)
In-Reply-To: <566B344A0B1AB14EB2486D887B6FF9E033AFEBBA17@SRV01.ARTech.local>

Hi Matthias,

On Tue, 13 Dec 2016 20:40:59 +0100
Matthias Auchmann <m.auchmann@artech.at> wrote:

> Hi guys!
> 
> I'm trying to use UBI and UBIFS on a Micron MT29F32G08ABCDBJ4 SLC NAND with an erase block size 4MB.

Woh! an SLC NAND with 4MB eraseblocks, that's surprizing.

> 
> First of all, mkfs.ubifs wouldn't support a LEB larger than UBIFS_MAX_LEB_SZ being (2*1024*1024).

This is the easy part ;). We already have patches to increase the limit
in different ubi utils (IIRC, it's also needed in ubinize).

> 
> When I use ubiattach though, it seems to be quite happy, giving me that on a 128MB partition:
> 
> UBI device number 0, total 32 LEBs (133169152 bytes, 127.0 MiB), available 8 LEBs (33292288 bytes, 31.8 MiB), LEB size 4161536 bytes (4.0 MiB)
> 
> Anyway, when I detach and reattach, it won't work. Details are in the bottom of that mail, but since I haven't thoroughly looked into it myself yet, this is only for those who care... I don't want to ask preliminary questions.
> 
> Anyway, my questions I guess then are:
> -) Are there any patches/branches that enable UBIFS to be run with a LEB of 4161536?
> -) Are there any known limitations with using a 4MiB PEB with UBI itself, or shall I assume for now that the problem is on my board/NAND driver regarding the above ubiattach errors upon the second attach?

I don't think so. We did several tests on different MLC NANDs exposing
4MB blocks, and the UBI/UBIFS layers were not complaining about that
(we had other problems related to the MLC constraints).
What's your controller?

Regards,

Boris

  parent reply	other threads:[~2016-12-14  7:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 19:40 UBI/UBIFS on NAND with PEB 4MB Matthias Auchmann
2016-12-13 19:52 ` Matthias Auchmann
2016-12-14  7:43 ` Boris Brezillon [this message]
2016-12-14  8:59   ` Matthias Auchmann
2017-04-11  9:26     ` Matthias Auchmann
2017-04-11 11:25       ` AW: " Markus Macsek

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=20161214084303.0059cbf5@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=m.auchmann@artech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox