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 11:50:23 +0200 [thread overview]
Message-ID: <1238061023.3321.67.camel@localhost.localdomain> (raw)
In-Reply-To: <20090326074443.GA7842@cloud.net.au>
On Thu, 2009-03-26 at 18:44 +1100, Hamish Moffatt wrote:
> Yes our version 1 media is from pre-mainline UBIFS and we took our
> chances by including it. We are shipping one product using 2.6.24 with
> old backported UBIFS and it's working very well. I don't have any
> expectations of support for the old version, so thanks for your
> assistance thus far.
>
> Fortunately the kernel upgrade is for a newer product where we have some
> more flexibility in fixing this problem.
>
> We can upgrade our boot loader to 2.6.29 also so that it can read UBIFS
> v4 media. This has to be co-ordinated with the main firmware image but
> this is reasonable.
>
> We do have one volatile UBIFS volume that we want to preserve. Is there
> any way we could convert it? For example a user-space utility that could
> read the old media version?
I was looking at the version changes, and this bugfix:
http://git.infradead.org/users/dedekind/ubifs-historical-3.git?a=commit;h=b9903987e8efb5252b692ffc7c2b190f4a0e83b8
makes it very difficult to turn old image into new one. This will
basically mean we need:
1. extract files from the old image
2. feed them to mkfs.ubifs.
> Maybe before upgrade we could run mkfs.ubifs using the contents of the
> existing volume to create the new format, unmount it and ubiupdatevol it..
The easiest way to do this is to boot the old kernel,
e.g. in vmware, extract the files using the nandsim technique:
http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_nandsim
then feed them to mkfs.ubifs.
But yes, a user-space utility to extract files from an image would be
of course nicer, but again it is something which is not easy to do.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-03-26 9:52 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
2009-03-26 7:44 ` Hamish Moffatt
2009-03-26 9:50 ` Artem Bityutskiy [this message]
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=1238061023.3321.67.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