From: Richard Weinberger <richard@nod.at>
To: "Egli, Samuel" <samuel.egli@siemens.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: autoresize causes insufficient reservation of PEBs for bad PEB handling
Date: Tue, 07 Jul 2015 21:43:23 +0200 [thread overview]
Message-ID: <559C2BDB.6070509@nod.at> (raw)
In-Reply-To: <27E9275BC1C8554E840881B19B62BE421A932C@DENBGAT9EI1MSX.ww902.siemens.net>
Am 07.07.2015 um 13:27 schrieb Egli, Samuel:
>>>
>>> Well, in my opinion it is a workaround to define all 3 vol_size's But
>>> I would like to use the "autoresize" flag for the 3rd volume.
>>> And I'm just worried that something else is not working properly
>>> because I think it should work also with autoresize.
>>
>> Ah, I thought the issue is gone. But you still get the error that UBI
>> wants 80 PEBs, but gets only 40?
>>
> That's correct. When I use "autoresize" flag, independently of defining
> the vol_size of the configuration volume, it will reserve only 40 PEBs
> instead of 80 when mounting the first time.
Hm, I'm a bit puzzled because the resize operation happens after the warning
you're facing.
Maybe Artem has an idea, I suspect some tooling issue.
Thanks,
//richard
prev parent reply other threads:[~2015-07-07 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 11:04 autoresize causes insufficient reservation of PEBs for bad PEB handling Egli, Samuel
2015-07-06 21:39 ` Richard Weinberger
2015-07-07 7:57 ` Egli, Samuel
2015-07-07 21:09 ` Richard Weinberger
2015-07-08 7:26 ` Egli, Samuel
2015-07-09 10:23 ` Egli, Samuel
2015-07-09 10:29 ` Richard Weinberger
2015-07-07 10:50 ` Richard Weinberger
2015-07-07 10:59 ` Egli, Samuel
2015-07-07 11:04 ` Richard Weinberger
2015-07-07 11:19 ` Egli, Samuel
2015-07-07 11:24 ` Richard Weinberger
2015-07-07 11:27 ` Egli, Samuel
2015-07-07 19:43 ` Richard Weinberger [this message]
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=559C2BDB.6070509@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=samuel.egli@siemens.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