public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs version 1 compatibility
Date: Thu, 26 Mar 2009 08:34:57 +0200	[thread overview]
Message-ID: <1238049297.3321.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20090326051508.GA4760@cloud.net.au>

On Thu, 2009-03-26 at 16:15 +1100, Hamish Moffatt wrote:
> Hi Artem and all,
> 
> I'm upgrading my embedded system which uses UBIFS from 2.6.24 (with a
> slightly updated ubifs) to 2.6.29.
> 
> I notice that the new kernel won't read my existing file systems as it
> says they are too old - version 1. The code checks for version 3 or 4 I
> see.
> 
> My application firmware is generated with mkfs.ubifs and programmed via
> ubiupdatevol, but the boot loader on my devices is based on the older
> kernel and won't be able to read it. And I have read-write file systems
> that will be formatted with the old version too.
> 
> 
> Is there any solution?

I've took a brief look. UBIFS went into mainline with format version 4,
and versions 1,2,3 were more development versions. There were changes in
the truncation node format and in inode node format. I would probably
be possible to have compatibility mode, but it is big job :-(

Your boot-loader is Linux kernel-based, right? Does it have write
support, or it is read-only?

Is it possible to upgrade the boot-loader at the same time you upgrade
the kernel on your devices?

Side note: now when u-boot supports UBIFS, we need to re-think our
versioning scheme and strictly preserve R/O compatibility.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  parent reply	other threads:[~2009-03-26  6:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  5:15 ubifs version 1 compatibility Hamish Moffatt
2009-03-26  6:02 ` Artem Bityutskiy
2009-03-26  6:34 ` Artem Bityutskiy [this message]
2009-03-26  7:44   ` Hamish Moffatt
2009-03-26  9:50     ` Artem Bityutskiy
2009-03-26 12:04       ` Hamish Moffatt
2009-03-26 12:12         ` Artem Bityutskiy
2009-03-26 13:15           ` Hamish Moffatt
2009-03-31  6:23             ` 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=1238049297.3321.20.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=hamish@cloud.net.au \
    --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