public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2 with sync burst mode
Date: Fri, 11 Mar 2005 12:27:30 +0100	[thread overview]
Message-ID: <20050311112730.GC11203@synertronixx3> (raw)
In-Reply-To: <42317DD7.3090205@yandex.ru>

Am 2005-03-11 14:15 +0300 schrieb Artem B. Bityuckiy:
> Konstantin Kletschke wrote:
> > The "Name CRC failed on node at ..." is away. I populated the root-fs
> Good.

But is moving the memcpy function a valid fix? There must be something
really wrong which should be fixed :/ DCache corruption i.e. missing
invalidating at the right time?

> 
> > root-fs. No problems. But mounting takes ages :)
> How much time does "ages" mean ?
> Do you stand that it was faster before?

Sorry, my apologies! CONFIG_MTD_DEBUG_VERBOSE was on 2, on 0 I get
reasonable mount time again, I am very sorry for misleading you!

> How large is your flash?

16MB, the root-fs is 5MB...

> Do you have directories with huge files number in it (say, ~ 10000)?

No.

> A: This means that flash_eraseall ought to write special node called 
> cleanmarker at the beginning of each block.

> If you are sure that the problem is not your slow flash driver, you 
> might try Ferenc's "summary" patch.

But if I understood correct the not created-cleanmarkers-by-bootloader
problem is "solved" on second boot? I see this here also, the 1st mount
takes ages, the following are fast.

Regards, sorry, Konstantin

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

  reply	other threads:[~2005-03-11 11:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 10:44 jffs2 with sync burst mode Konstantin Kletschke
2005-03-11 11:15 ` Artem B. Bityuckiy
2005-03-11 11:27   ` Konstantin Kletschke [this message]
2005-03-11 11:59     ` Artem B. Bityuckiy
2005-03-11 11:57 ` Konstantin Kletschke
  -- strict thread matches above, loose matches on Subject: below --
2005-03-09 13:14 Konstantin Kletschke
2005-03-10 13:15 ` Artem B. Bityuckiy
2005-03-10 15:22   ` Konstantin Kletschke
2005-03-10 15:54     ` Artem B. Bityuckiy
2005-03-10 16:40       ` Konstantin Kletschke
2005-03-10 19:25         ` Steve Wahl
2005-03-10 23:24           ` Konstantin Kletschke
2005-03-10 15:46   ` Konstantin Kletschke
2005-03-10 16:21     ` Artem B. Bityuckiy
2005-03-10 16:48       ` Konstantin Kletschke
2005-03-10 17:08         ` Artem B. Bityuckiy
     [not found]         ` <JPEALJAFNGDDLOPNDIEECEJFDBAA.joakim.tjernlund@lumentis.se>
2005-03-10 23:18           ` Konstantin Kletschke
     [not found]             ` <BCEFJBPJCGFCNMMMIDBHEEPKCKAA.Joakim.Tjernlund@lumentis.se>
2005-03-11  0:03               ` Konstantin Kletschke
2005-03-10 17:02       ` Konstantin Kletschke
2005-03-10 17:17         ` Artem B. Bityuckiy
2005-03-10 18:27           ` Konstantin Kletschke
2005-03-10 18:53           ` Konstantin Kletschke

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=20050311112730.GC11203@synertronixx3 \
    --to=lists@ku-gbr.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