From: David Woodhouse <dwmw2@infradead.org>
To: Sherwin Liu <sherwinliu@sbcglobal.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: REF_PRISTINE node ...
Date: Wed, 19 Nov 2003 17:09:35 +0000 [thread overview]
Message-ID: <1069261772.31205.26.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <20031119163841.9458.qmail@web80503.mail.yahoo.com>
On Wed, 2003-11-19 at 08:38 -0800, Sherwin Liu wrote:
> "REF_PRISTINE node at XX had a previous non-hole frag
> in the same page. Tell dwmw2."
>
> Is this just a debugging message, or is it an
> indication of something wrong?
It's basically harmless, and should be gone if you update to the current
CVS JFFS2 code.
A while ago, I implemented a garbage-collection optimisation; if a node
is expected to be identical when we write out a replacement, we can
avoid decompressing and recompressing it if we just copy the whole thing
intact. So I start keeping track of such 'pristine' nodes which were an
optimal representation of their data... and that message warns me of one
case where such a node marked REF_PRISTINE but shouldn't have been.
--
dwmw2
prev parent reply other threads:[~2003-11-19 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:38 REF_PRISTINE node Sherwin Liu
2003-11-19 17:09 ` David Woodhouse [this message]
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=1069261772.31205.26.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sherwinliu@sbcglobal.net \
/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