public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* UBIFS incompatibilities due to min_io_size adaptions?
@ 2011-01-26 14:20 Holger Brunck
  2011-01-26 15:49 ` Artem Bityutskiy
  0 siblings, 1 reply; 2+ messages in thread
From: Holger Brunck @ 2011-01-26 14:20 UTC (permalink / raw)
  To: linux-mtd@lists.infradead.org; +Cc: Andreas Huber

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-01-26 16:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-26 14:20 UBIFS incompatibilities due to min_io_size adaptions? Holger Brunck
2011-01-26 15:49 ` Artem Bityutskiy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox