From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Jon Ringle <jon@ringle.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: can't mount ubifs after resizing with ubirsvol
Date: Mon, 5 Sep 2011 10:33:03 +0200 [thread overview]
Message-ID: <4E64893F.5000204@parrot.com> (raw)
In-Reply-To: <CAMwGMjxX4q2oYt-KDwoq87WP77Phbd+xEdUyL-VkaLLvYCeqfA@mail.gmail.com>
Hi,
Jon Ringle a écrit :
> Hi,
>
> I have a ubi0 with a static squashfs part and a ubifs part. Sometimes
> I have to update the squashfs with an image that is bigger than the
> currently allocated space for the squashfs part. My plan was to use
> ubirsvol to reduce the size of the ubifs part, then use ubirsvol in
> increase the size of the squashfs part so that it is big enough for
> ubiupdatevol to accept the new image in the squashfs part.
>
> But when I try to mount ubifs after resizing, it complains with:
> (initramfs)[/]# mount -t ubifs ubi0:ubifs /mnt
> [ 1838.350000] UBIFS error (pid 621): validate_sb: bad LEB count: 866
> in superblock, 800 on UBI volume, 19 minimum required
> [ 1838.360000] UBIFS error (pid 621): validate_sb: bad superblock, error 1
> mount: mounting ubi0:ubifs on /mnt failed: Invalid argument
>
> Is what I want to do possible?
>
AFAIK you can't reduce size of ubifs volume, you can only increase it.
Matthieu
next prev parent reply other threads:[~2011-09-05 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 22:53 can't mount ubifs after resizing with ubirsvol Jon Ringle
2011-09-05 8:33 ` Matthieu CASTET [this message]
2011-09-11 13:17 ` Artem Bityutskiy
2015-11-09 14:04 ` Ibrahim Mattus Neto
2015-11-18 20:01 ` Richard Weinberger
2015-11-19 13:34 ` Ibrahim Mattus Neto
2015-11-19 13:42 ` Richard Weinberger
2015-11-19 14:09 ` Konstantin Tokarev
2015-11-19 15:02 ` Richard Weinberger
2015-11-20 0:09 ` Dongsheng Yang
[not found] ` <564DEEEF.7010102@writesys.com.br>
2015-11-22 21:43 ` Richard Weinberger
2015-11-23 13:43 ` Ibrahim Mattus Neto
2011-09-09 9:59 ` marco
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=4E64893F.5000204@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=jon@ringle.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.