From: Holger Brunck <holger.brunck@keymile.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: Andreas Huber <andreas.huber@keymile.com>
Subject: UBIFS incompatibilities due to min_io_size adaptions?
Date: Wed, 26 Jan 2011 15:20:23 +0100 [thread overview]
Message-ID: <4D402DA7.8050101@keymile.com> (raw)
Hi all,
we use UBI and UBIFS on NOR and NAND based systems and kernel 2.6.33. In the
last days we applied the latest UBI and MTD patches for the min I/O size.
Due to commit a121f643993474548fe98144514c50dd4f3dbe76 UBI: use
mtd->writebufsize to set minimal I/O unit size
now the min I/O size is equal to the writebuffersize of the flash.
This caused incompatibilites in the UBIFS. We have an UBIFS on a board on a NOR
flash created in the past without the patches. Now with a newer SW and a newer
kernel which has the latest fixes we can't mount the old UBIFS anymore.
UBIFS error (pid 865): validate_sb: min. I/O unit mismatch: 8 in superblock, 64 real
UBIFS error (pid 865): validate_sb: bad superblock, error 1
mount: wrong fs type, bad option, bad superblock on ubi0:cfg,
missing codepage or other error
If we reformate the UBIFS everything is ok, but we got a problem with the older
SW image:
UBIFS error (pid 865): validate_sb: min. I/O unit mismatch: 64 in
superblock, 8 real
UBIFS error (pid 865): validate_sb: bad superblock, error 1
mount: wrong fs type, bad option, bad superblock on ubi0:cfg,
missing codepage or other error
Is there a way to solve this problem? I do not hope that the only solution is to
remove these patch.
Any help is appreciated.
Best regards
Holger Brunck
next reply other threads:[~2011-01-26 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 14:20 Holger Brunck [this message]
2011-01-26 15:49 ` UBIFS incompatibilities due to min_io_size adaptions? Artem Bityutskiy
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=4D402DA7.8050101@keymile.com \
--to=holger.brunck@keymile.com \
--cc=andreas.huber@keymile.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;
as well as URLs for NNTP newsgroup(s).