From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jeff Angielski <jeff@theptrgroup.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach fails with "bad image sequence number"
Date: Sun, 10 Jan 2010 01:53:11 +0200 [thread overview]
Message-ID: <1263081191.7315.121.camel@localhost.localdomain> (raw)
In-Reply-To: <1263081089.7315.119.camel@localhost.localdomain>
On Sun, 2010-01-10 at 01:51 +0200, Artem Bityutskiy wrote:
> Hi,
>
> On Mon, 2009-12-21 at 17:33 -0500, Jeff Angielski wrote:
> > If I ubiformat my NAND partition with an UBIFS image I keep on getting
> > "bad image sequence number" when I try to do the ubiattach. If I just
> > do a plain ubiformat with no image then everything works fine when I
> > ubiattach.
> >
> > I was wondering if somebody ran into something similar. The steps are
> > so trivial it seems like something fundamentally wrong with either the
> > mkfs.ubifs or the ubiformat.
> >
> > I did not see anything related to this on the UBFI FAQ or documentation.
>
> I believe this is an ubiformat bug. Thanks for reporting and sorry for
> inconvenience.
>
> I attach and inline 2 patches which should fix this. I cannot have a
> possibility to test them now, so they are untested. They are against the
> latest mtd-utils.git (commit a4e502d99129da8ebba6d40b373a4422a175e9af).
Could you please try them and report if they fix your problem or not?
P.S. when we fix this, we'll have to tag a new mtd-utils version, since
this is a very bad bug.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-01-09 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 22:33 ubiattach fails with "bad image sequence number" Jeff Angielski
2010-01-09 23:51 ` Artem Bityutskiy
2010-01-09 23:53 ` Artem Bityutskiy [this message]
2010-01-13 3:26 ` Jeff Angielski
2010-01-15 17:15 ` Artem Bityutskiy
2010-01-16 13:22 ` Peter Korsgaard
2010-01-26 9:47 ` Peter Korsgaard
2010-01-28 18:56 ` David Woodhouse
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=1263081191.7315.121.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=jeff@theptrgroup.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