From: syed khader <sk.syed@yahoo.com>
To: "J�rn" Engel <joern@wohnheim.fh-wedel.de>,
syed khader <sk.syed@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: zlib compression is failing
Date: Wed, 17 May 2006 04:22:39 -0700 (PDT) [thread overview]
Message-ID: <20060517112239.31511.qmail@web37915.mail.mud.yahoo.com> (raw)
In-Reply-To: <20060517091038.GA22457@wohnheim.fh-wedel.de>
Hi
I have uClinux2.4.24(which corresponds to 2.4
kernel). It originally had jffs2.1. Since 2.1 was
quite slow, we moved it to jffs2.2 by applying patch
from mtd cvs as follows:
cvs -d :pserver:anoncvs@cvs.infradead.org:/home/cvs
login (password: anoncvs)
cvs -d :pserver:anoncvs@cvs.infradead.org:/home/cvs
co mtd
cd <mtd-path>/patches
sh patchin.sh -c -j <kernel-path>
The CVS tag was D2004.05.11.18.30.00
After applying the patch I am seeing the CRC errors.
As per the logs there were zlib error messages which I
thought were the reason behind CRC errors.
Regarding this link you dont need to register: you can
select free service and download the file directly
http://rapidshare.de/files/20655260/jffs2crclog.txt.html
--- J�rn Engel <joern@wohnheim.fh-wedel.de> wrote:
> Side note: You might want to read the list
> etiquette. Open source
> taste is a bit different and usually frowns upon
> things that are
> perfectly acceptable in companies. In particular,
> when writing mails
> you should only quote relevant bits from the last
> mail, remove
> everything else, and write your answers underneith
> the quoted text you
> are referring to. And here is the full thing:
> http://www.infradead.org/~dwmw2/email.html
>
> On Tue, 16 May 2006 23:25:52 -0700, syed khader
> wrote:
> >
> > in the logs I am seeing the following error
> > messages:
> >
> > zlib compressed 68 bytes into 77; failing
> >
> > why does zlib compression fail?
>
> When compressing data, there is always the chance
> that data is
> actually being _expanded_ instead of compressed.
> Imaging compressing
> a compressed file. Zlib has to add a small header
> and then tries to
> compress the data, which doesn't work. So it simply
> stores the data
> verbatim after the header, resulting in bigger data
> than before.
>
> When this happens, jffs2 doesn't want to store the
> bigger "compressed"
> data, but just the plain uncompressed data, saving a
> little flash
> space.
>
> Quite interesting, though, are the sizes. 68 bytes
> is exactly a jffs2
> inode header. It makes me a bit uneasy if that
> cannot be compressed.
> So maybe it is time to finally ask some basic
> questions:
> o What kernel version are you using?
> o Are there any patches on top of it?
> o Is the mtd/jffs2 code from above kernel version or
> from cvs/git?
>
> > > Here is the link to the log:
> > >
> >
>
http://rapidshare.de/files/20655260/jffs2crclog.txt.html
>
> I just see a page telling me to subscribe to some
> service. Don't you
> have some other webspace you could use?
>
> J�rn
>
> --
> I've never met a human being who would want to read
> 17,000 pages of
> documentation, and if there was, I'd kill him to get
> him out of the
> gene pool.
> -- Joseph Costello
>
>
______________________________________________________
> Linux MTD discussion mailing list
>
http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-05-17 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060516061354.GA18958@wohnheim.fh-wedel.de>
2006-05-16 12:40 ` CRC errors when continuous fseek/fputs on JFFS2 syed khader
2006-05-16 14:26 ` Jörn Engel
2006-05-16 15:01 ` syed khader
2006-05-16 15:31 ` Jörn Engel
2006-05-17 5:12 ` syed khader
2006-05-17 6:25 ` zlib compression is failing syed khader
2006-05-17 9:10 ` Jörn Engel
2006-05-17 10:42 ` Josh Boyer
2006-05-17 11:22 ` syed khader [this message]
2006-05-17 13:19 ` Jörn Engel
2006-05-17 13:48 ` syed khader
2006-05-17 14:28 ` David Woodhouse
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=20060517112239.31511.qmail@web37915.mail.mud.yahoo.com \
--to=sk.syed@yahoo.com \
--cc=joern@wohnheim.fh-wedel.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