From: Thomas Brandt <brandt@bury.com>
To: linux-mtd@lists.infradead.org
Subject: Master node recovery /corruption
Date: Mon, 18 Mar 2013 16:42:38 +0100 [thread overview]
Message-ID: <514735EE.5050806@bury.com> (raw)
Hi,
I've a little question regarding the recovery of a master node.
In my case the first master node was corrupted and could not be recovered.
After taking a look to the code:
/fs/ubifs/recovery.c
int ubifs_recover_master_node(struct ubifs_info *c)
{
void *buf1 = NULL, *buf2 = NULL, *cor1 = NULL, *cor2 = NULL;
struct ubifs_mst_node *mst1 = NULL, *mst2 = NULL, *mst;
const int sz = c->mst_node_alsz;
int err, offs1, offs2;
dbg_rcvry("recovery");
err = get_master_node(c, UBIFS_MST_LNUM, &buf1, &mst1, &cor1);
if (err)
goto out_free;
err = get_master_node(c, UBIFS_MST_LNUM + 1, &buf2, &mst2, &cor2);
if (err)
goto out_free;
I see that if getting the first master node fails the function returns
without trying to get the second master node, which should be as far as
I understand it, a mirror of the first master node?!.
Is there any reason why it must be handled in that way?
Because after I've done a little hack (don't care that first node fails)
ithe first master node was recovered from the second one and it could be
mounted without any errors.
At the moment it difficult for me to say whats right or wrong!?
Might there be a bug?
Cheers,
Thomas
next reply other threads:[~2013-03-18 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 15:42 Thomas Brandt [this message]
2013-03-25 8:34 ` Master node recovery /corruption Thomas Brandt
2013-04-15 15:34 ` 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=514735EE.5050806@bury.com \
--to=brandt@bury.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 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.