From: Norbert Federa <nfedera@thinstuff.com>
To: vherva@vianova.fi
Cc: linux-mtd@lists.infradead.org
Subject: Re: block2mtd: Overrun end of disk in cache readahead
Date: Wed, 05 Jul 2006 09:49:14 +0200 [thread overview]
Message-ID: <44AB6EFA.9000604@thinstuff.com> (raw)
In-Reply-To: <20060705072614.GQ6240@vianova.fi>
Ville,
Try changing the PAGE_READAHEAD define in
/drivers/mtd/devices/block2mtd.c from 64 to 0:
-#define PAGE_READAHEAD 64
+#define PAGE_READAHEAD 0
Or a bit more sophisticated:
in drivers/mtd/devices/Kconfig ...
+config MTD_BLOCK2MTD_PAGE_READAHEAD
+ int "How many pages block2mtd reads ahead"
+ depends on MTD_BLOCK2MTD
+ default "64"
+ help
+ This allows you to configure the PAGE_READAHEAD value of the
+ MTD_BLOCK2MTD driver.
+
... and in drivers/mtd/devices/block2mtd.c
-#define PAGE_READAHEAD 64
+#define PAGE_READAHEAD CONFIG_MTD_BLOCK2MTD_PAGE_READAHEAD
--
Norbert
Ville Herva wrote:
> I get
> block2mtd: Overrun end of disk in cache readahead
>
> each time I mount a JFFS2 created with
>
> mkfs.jffs2 -o IMAGE -d skeleton --pad=999161856 -v
> dd if=IMAGE of=/dev/hdc2
>
> Afaict, the fs should fit onto the device:
>
> du --block-size=512 --apparent-size IMAGE
> 1951488 IMAGE
> blockdev --getsize /dev/hdc2
> 1951488
> blockdev --getsize /dev/mtdblock0
> 1951488
>
> Should I leave some blocks worth of space in the end nevertheless?
>
>
>
>
> -- v --
>
> v@iki.fi
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2006-07-05 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 7:26 block2mtd: Overrun end of disk in cache readahead Ville Herva
2006-07-05 7:49 ` Norbert Federa [this message]
2006-07-05 10:07 ` Ville Herva
2006-07-05 11:22 ` Jörn Engel
2006-07-06 8:28 ` Ville Herva
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=44AB6EFA.9000604@thinstuff.com \
--to=nfedera@thinstuff.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vherva@vianova.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.