From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: JerinJacob <jerin.jacob@maxim-ic.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Hunter Adrian \(Nokia-D/Helsinki\)" <adrian.hunter@nokia.com>
Subject: Re: UBIFS Error
Date: Thu, 10 Sep 2009 15:13:47 +0300 [thread overview]
Message-ID: <4AA8ED7B.5020509@nokia.com> (raw)
In-Reply-To: <4AA8EA9C.4070805@maxim-ic.com>
On 09/10/2009 03:01 PM, ext JerinJacob wrote:
> Hi UBIFS-Dev,
>
> I am able to reproduce the problem with a C program. please find it below.
> Please find pseudo code for the same
> -----------------------------------------------------------------------------
> Step 1: Open 10 files for writing.
> Step 2: fill the files with random data, which size is less than
> (100KiB*2*10)
> Step 3: if total files size is greater than 500MiB then
> lseek file pointers to 0'th location
> Step 4: Goto 2
> ---------------------------------------------------------------------------------
Hi,
we'll look at this. But please, let us know which kernel version
you are using? Do you have all the latest UBIFS updates? I remember
we fixed a problem with similar symptoms at some point.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-09-10 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 6:02 UBIFS Error JerinJacob
2009-09-08 7:57 ` Adrian Hunter
2009-09-08 12:16 ` JerinJacob
2009-09-10 12:01 ` JerinJacob
2009-09-10 12:13 ` Artem Bityutskiy [this message]
2009-09-10 12:53 ` JerinJacob
2009-09-10 13:46 ` Artem Bityutskiy
2009-09-10 14:22 ` JerinJacob
2009-09-11 12:18 ` JerinJacob
2009-09-14 14:27 ` Artem Bityutskiy
2009-09-14 14:29 ` Artem Bityutskiy
2009-09-15 8:28 ` JerinJacob
2009-09-17 8:38 ` JerinJacob
2009-09-28 11:22 ` Artem Bityutskiy
2009-09-29 5:48 ` JerinJacob
2009-09-30 5:37 ` Artem Bityutskiy
2009-09-14 15:07 ` JerinJacob
2009-09-14 15:08 ` 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=4AA8ED7B.5020509@nokia.com \
--to=artem.bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=jerin.jacob@maxim-ic.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 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).