public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Jörg Krause" <joerg.krause@embedded.rocks>,
	linux-mtd@lists.infradead.org
Subject: Re: ubi_wl_get_peb: Unable to get a free PEB from user WL pool
Date: Wed, 5 Aug 2015 23:45:47 +0200	[thread overview]
Message-ID: <55C2840B.5000709@nod.at> (raw)
In-Reply-To: <1438810690.6328.26.camel@embedded.rocks>

Jörg,

Am 05.08.2015 um 23:38 schrieb Jörg Krause:
> On Mi, 2015-08-05 at 23:30 +0200, Richard Weinberger wrote:
>> Jörg,
>>
>> Am 05.08.2015 um 23:22 schrieb Jörg Krause:
>>> Hi,
>>>
>>> after updating a custom build Linux Kernel from 4.0.8 to 4.1.4 my
>>> system fails to attach an MTD partition. Note, that everything 
>>> worked
>>> fine with Linux Kernels before 4.1.
>>
>> UBI Fastmap saw a lot of changes in 4.1.
>>
>>> The error message is:
>>> 	ubi_wl_get_peb: Unable to get a free PEB from user WL pool
>>> 	autoresize: cannot auto-resize volume 0
>>
>> Can you please share the full kernel log?
>> Especially I'm interested in the fastmap pool sizes.
> 
> I attached the kernel boot log.

Thanks.
That's a really small UBI setup.
[    3.202421] ubi1: default fastmap pool size: 10
[    3.207174] ubi1: default fastmap WL pool size: 5

>>
>>> The MTD partition has a size of 36 MB. The UBIFS image is created 
>>> with:
>>> 	mkfs.ubifs -v -F -m 2048 -e 124KiB -c 264 -d user -o user.ubifs
>>>
>>> The UBI image is created with:
>>> 	ubinize -v -o data.ubi -m 2048 -p 128KiB ubinize.ini
>>>
>>> ubinize.ini:
>>>     [user]
>>>     mode=ubi
>>>     image=user.ubifs
>>>     vol_id=0
>>>     vol_type=dynamic
>>>     vol_name=user
>>>     vol_flags=autoresize
>>>
>>>
>>> It works, if I replace the vol_flags with vol_size=32480KiB. But 
>>> that's
>>> not a final solution for me.
>>>
>>> Any idea what is wrong here?
>>
>> Not sure. Maybe fastmap claims too much PEBs.
>> BTW: Are you actually using fastmap or is it just enabled in your 
>> kernel config?
> 
> It is enabled in the kernel config. Not sure how to use it.

Then just disable it. :)
Meanwhile I'll find out what exactly is going on.

Thanks,
//richard

  reply	other threads:[~2015-08-05 21:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 21:22 ubi_wl_get_peb: Unable to get a free PEB from user WL pool Jörg Krause
2015-08-05 21:30 ` Richard Weinberger
2015-08-05 21:38   ` Jörg Krause
2015-08-05 21:45     ` Richard Weinberger [this message]
2015-08-05 21:53       ` Jörg Krause
2015-08-05 22:01         ` Richard Weinberger
2015-08-05 22:17           ` Jörg Krause
2015-08-06  7:30             ` Richard Weinberger
2015-08-06  8:10               ` Jörg Krause
2015-08-06  8:12                 ` Richard Weinberger
2015-08-06 18:16                 ` Richard Weinberger
2015-08-06 18:43                   ` Jörg Krause

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=55C2840B.5000709@nod.at \
    --to=richard@nod.at \
    --cc=joerg.krause@embedded.rocks \
    --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