From: Richard Weinberger <richard@sigma-star.at>
To: Frank Erdrich <frank@erdrich.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS - ubifs_get_pnode.part.4: error -22 reading pnode
Date: Thu, 05 Apr 2018 00:36:01 +0200 [thread overview]
Message-ID: <1874641.K4bY7NcptO@blindfold> (raw)
In-Reply-To: <fac82fd0-1c68-8ea7-d066-65c5901ff539@erdrich.net>
Frank,
Am Mittwoch, 4. April 2018, 06:58:40 CEST schrieb Frank Erdrich:
> > Can you reproduce the issue?
> > If so, please retry with the attached patches.
> > They will not fix your already broken UBIFS but they (hopefully) will
> > make sure that the accounting problem will not happen again.
>
> That's the biggest problem. There is no way to reproduce it on a proper
> way. The only thing I can do at the moment is to write to the partition
> and do random power-cuts.
>
> I will try the patches you have provided an will check if the error
> comes up with them or not. Unluckily I'm out of office for today, so I
> can start testing tomorrow.
>
> > Can you also share me the broken UBIFS image?
>
> I have to talk to our customer if that is ok for him, but I think that
> will not be a big problem. Can you give me a command line to extract
> that image from the flash in a way, that it is directly usable by you
> without do conversion stuff?.
In this case I'm just interested in UBIFS itself.
So you can directly dd/cat from /dev/ubiX_Y.
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
prev parent reply other threads:[~2018-04-04 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 8:28 UBIFS - ubifs_get_pnode.part.4: error -22 reading pnode Erdrich, Frank
2018-04-03 12:04 ` Richard Weinberger
[not found] ` <s1l9q5oc97q87j6d75pkp49b.1522781343251@email.android.com>
2018-04-03 20:26 ` Frank Erdrich
2018-04-03 21:28 ` Richard Weinberger
2018-04-04 4:58 ` Frank Erdrich
2018-04-04 22:36 ` Richard Weinberger [this message]
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=1874641.K4bY7NcptO@blindfold \
--to=richard@sigma-star.at \
--cc=frank@erdrich.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.