From: Artem Bityutskiy <dedekind1@gmail.com>
To: Tanya Brokhman <tlinder@codeaurora.org>
Cc: Dolev Raviv <draviv@codeaurora.org>, linux-mtd@lists.infradead.org
Subject: Re: ubifs: assertion fails
Date: Mon, 07 Apr 2014 14:43:36 +0300 [thread overview]
Message-ID: <1396871016.17040.33.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <533A5407.4060900@codeaurora.org>
On Tue, 2014-04-01 at 08:52 +0300, Tanya Brokhman wrote:
> The log isn't flooded with the above mentioned error, but it does repeat
> several times.
Even though you do a lot of I/O operations?
If the accounting becomes incorrect, I think you'd see a warning for
each and every I/O operations.
Also, do you have several UBIFS file-systems mounted?
> Is there any way we can help in debugging and fixing this? Also, we're
> running on a 3.10 based kernel and I saw a lot of patches that change
> the shrinker after 3.10 on linux-next. What kernel version did you see
> the shrinker errors on?
Well, you just need to stress the shrinker. I did it by simply adding a
hack to ubifs module init which kmalloc()'ed a lot of memory. Not
too-much, but enough to cause some pressure when doing a lot of I/O
operations and get UBIFS shrinker be invoked. This took me some amount
of time to get a good hack. I use a normal PC with some Fedora, and
nandsime. This makes it a lot easier to debug, comparing with doing this
on a real target. After all, shrinker is a generic component. I think
that PC had 4GB of RAM. I do not remember how much I allocated in my
hack.
I think I used older version than 3.10 back then.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-04-07 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 6:03 ubifs: assertion fails Dolev Raviv
2014-03-31 10:14 ` Artem Bityutskiy
2014-04-01 5:52 ` Tanya Brokhman
2014-04-07 11:43 ` Artem Bityutskiy [this message]
2014-04-27 12:12 ` Dolev Raviv
2014-05-29 1:55 ` hujianyang
2014-05-29 7:24 ` Dolev Raviv
2014-05-29 7:42 ` 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=1396871016.17040.33.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=draviv@codeaurora.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tlinder@codeaurora.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;
as well as URLs for NNTP newsgroup(s).