public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Cal Page <pagcal@runbox.com>
To: "Ostendorf, Rainer" <Rainer.Ostendorf@BENNING.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problems with JFFS2 FS during parallel write operations
Date: Mon, 01 Dec 2008 07:08:21 -0500	[thread overview]
Message-ID: <4933D3B5.9070507@runbox.com> (raw)
In-Reply-To: <0F0EC10F42A3384392AE60EF2A660B40427D98@tbbsrv56>

You might check the locks in mtd. I noticed they were pretty low. It 
might make sense in your case to move them to mtdpart.c or even up into 
yaffs_mtdif2.c for the read/write/erase functions.

Cal Page

Ostendorf, Rainer wrote:
> Hi list,
>
> i'm still working on the problem described in my previous post:
>
> [...]
>   
>> During normal operation the system runs perfectly stable, but when i 
>> start two processes running parallel, writing huge amounts of data 
>> to the flash device, i get error 
>> messages from the JFFS2 filesystem:
>>
>> ...
>> argh. node added in wrong place
>> argh. node added in wrong place
>> ...
>>
>> This message repeats for about 15-20 times while copying parallel 2 
>> files of about 6MByte to the flash via Ethernet (SCP). 
>>     
> [...]
>
> As i can only reproduce the corruption of the JFFS2 FS during parallel access of at leat two processes writing to the flash, i assume that the cause for the corruption is some kind of race-condition. Have there been any known problems/bugs with race conditions, that could lead to an error like this? Would it probably help to upgrade to a newer kernel version? Any hint and help would be greatly appreciated.
>
> best regards,
> Rainer
>
>
> Benning Elektrotechnik und Elektronik GmbH & Co. KG Bocholt
> Handelsregister Coesfeld HRA-Nr. 4661
> Persönlich haftende Gesellschaft: Benning GmbH
> Handelsregister Coesfeld HRB-Nr. 7772
> Geschäftsführer: Th. Benning
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
>   

  reply	other threads:[~2008-12-01 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05  8:43 Problems with JFFS2 FS during parallel write operations Ostendorf, Rainer
2008-12-01  7:36 ` Ostendorf, Rainer
2008-12-01 12:08   ` Cal Page [this message]
2008-12-01 12:48   ` Geert Uytterhoeven

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=4933D3B5.9070507@runbox.com \
    --to=pagcal@runbox.com \
    --cc=Rainer.Ostendorf@BENNING.de \
    --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