From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: Richard Weinberger <richard@nod.at>
Subject: Re: master node can not be recovered
Date: Tue, 03 Nov 2015 10:32:19 +0200 [thread overview]
Message-ID: <1446539539.6126.110.camel@gmail.com> (raw)
In-Reply-To: <A765B125120D1346A63912DDE6D8B6310BF4FB2A@NTXXIAMBX02.xacn.micron.com>
On Mon, 2015-11-02 at 16:10 +0000, Bean Huo 霍斌斌 (beanhuo) wrote:
> Hi, Richard
> I tested my UBI power loss solution, have a question about master
> node.
> We all know that if master node be corrupted by power loss , we can
> recover it by second one. But from my testing results, in fact,
> It cannot be recovered by second backup master node. If first master
> node be corrupted by power loss, this relevant block will be
> correctly read, get_master_node will not reture 0, so next time
> recover operation will not run.
> Or I'm wrong?
There are debugging messages, can you please try to enable them and
share the resutl, so that we could see what was going on?
prev parent reply other threads:[~2015-11-03 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 16:10 master node can not be recovered Bean Huo 霍斌斌 (beanhuo)
2015-11-02 16:46 ` Richard Weinberger
2015-11-03 9:12 ` Artem Bityutskiy
2015-11-04 7:43 ` Bean Huo 霍斌斌 (beanhuo)
2015-11-04 8:03 ` Richard Weinberger
2015-11-04 8:20 ` Artem Bityutskiy
2015-11-04 8:25 ` Bityutskiy, Artem
2015-11-04 8:40 ` Boris Brezillon
2015-11-04 8:57 ` Artem Bityutskiy
2015-12-04 7:51 ` Bean Huo 霍斌斌 (beanhuo)
2015-11-03 8:32 ` Artem Bityutskiy [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=1446539539.6126.110.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=beanhuo@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.