From: Artem Bityutskiy <dedekind1@gmail.com>
To: Wolfgang Wegner <wolfgang@leila.ping.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS oops after remount ro
Date: Mon, 29 Nov 2010 16:21:09 +0200 [thread overview]
Message-ID: <1291040469.2141.10.camel@koala> (raw)
In-Reply-To: <20101129131807.GB23237@leila.ping.de>
On Mon, 2010-11-29 at 14:18 +0100, Wolfgang Wegner wrote:
> Hi Artem,
>
> I can now reproduce the Oops with CONFIG_UBIFS_FS_DEBUG and your
> patch.
OK, I thought one of ubi_asserts() would trigger. They do not.
> However, I had to manually apply the hunks because my tree
> seems to differ enough for patch to not apply it automatically...
I sent the patch against the ubifs-v2.6.32 tree, which has all the UBIFS
patches back-ported, and which I recommend to use:
http://linux-mtd.infradead.org/doc/ubifs.html#L_source
(hmm, need to update that page, now there are more back-port trees)
> And here is the complete console log in case I missed some
> important information:
Well, because of the ps output, it is difficult to read kernel prints.
Also, the situation becomes more difficult because you have several
UBIFS file-systems, so many messages are irrelevant. Would be nice to
print them only for the instance which oopses.
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
> qqq: kupdated for ubifs
So, not 100% sure, but probably this is kuptdated writeback. For some
reason mm thinks ubifs has dirty data, although it should not have,
because re-mounting path has full sync.
> qqq: writing inode 3298
Does this always happen for inode 3298? Or the inode number changes?
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-11-29 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 13:50 UBIFS oops after remount ro Wolfgang Wegner
2010-11-26 15:24 ` Artem Bityutskiy
2010-11-26 17:29 ` Wolfgang Wegner
2010-11-29 13:18 ` Wolfgang Wegner
2010-11-29 14:21 ` Artem Bityutskiy [this message]
[not found] ` <20101129151729.GE23237@leila.ping.de>
[not found] ` <1291049157.2141.17.camel@koala>
2010-11-29 17:02 ` Wolfgang Wegner
2010-11-29 17:23 ` Wolfgang Wegner
2010-12-02 3:35 ` Artem Bityutskiy
2010-12-02 3:41 ` Artem Bityutskiy
2010-12-02 9:17 ` Wolfgang Wegner
2010-12-02 12:20 ` 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=1291040469.2141.10.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=wolfgang@leila.ping.de \
/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;
as well as URLs for NNTP newsgroup(s).