From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 BUG() on mount
Date: Tue, 04 Apr 2006 11:34:30 +0400 [thread overview]
Message-ID: <44322186.3060800@yandex.ru> (raw)
In-Reply-To: <20060403154933.GA18475@orphique>
Ladislav Michl wrote:
> jffs2_scan_inode_node adds also inodes with zero nlink to
> unchecked_space, but jffs2_garbage_collect_pass skips them. That
> probably leads to above problem. After applying following patch
> BUG() is no longer triggered.
>
<snip>
> I'm not sure what is correct solution. With this change there are lots of
> JFFS2 warning: (138) jffs2_get_inode_nodes: Eep. No valid nodes for ino #465.
> JFFS2 warning: (138) jffs2_do_read_inode_internal: no data nodes found for ino #465
> Returned error for crccheck of ino #465. Expect badness...
> warnings. Jffs2 summary feature is disabled. I'd be very gratefull for ideas.
Actually, there is a jffs2_build_filesystem() function which walks all
inodes with nlink == 0 and pretends to dispense with them. I believe
that function is the right place to fix. I ganced at it, and it appeared
to be thet it calls jffs2_mark_node_obsolete() for all nodes of this
inode. jffs2_mark_node_obsolete() is a huge and fearsom monster-function
which may do something wrong.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2006-04-04 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 11:54 jffs2 Oops on mount Ladislav Michl
2006-03-22 19:49 ` Ladislav Michl
2006-03-23 18:25 ` jffs2 BUG() " Ladislav Michl
2006-04-03 15:49 ` Ladislav Michl
2006-04-04 7:34 ` Artem B. Bityutskiy [this message]
2006-04-10 9:09 ` Ladislav Michl
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=44322186.3060800@yandex.ru \
--to=dedekind@yandex.ru \
--cc=ladis@linux-mips.org \
--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