From: David Woodhouse <dwmw2@infradead.org>
To: Brian T <btuch@usa.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 file corruption
Date: Tue, 31 Aug 2004 21:00:09 +0100 [thread overview]
Message-ID: <1093982409.6200.54.camel@localhost.localdomain> (raw)
In-Reply-To: <082b01c48f94$fe637840$fd0ba8c0@briantpc>
On Tue, 2004-08-31 at 14:59 -0500, Brian T wrote:
> > Putting them up for download is probably better than mailing them to the
> > list -- yes.
> >
> > Make sure that your log includes KERN_DEBUG messages and isn't lossy.
> > Remote syslog isn't necessarily good enough -- a serial console
> > certainly is.
> >
> > Let me know the inode number of the test file you created too (ls -i me)
> >
>
> I got console logging on, and will run some tests. I'll send you a priv
> email where to get the files from.
>
> With KERN_DEBUG (all options) on, I don't see anything extra in the syslog.
> Should there be?
man syslogd.conf
syslog doesn't log messages at KERN_DEBUG by default. But syslog is too
lossy anyway. Use a serial console.
Use CONFIG_JFFS2_FS_DEBUG=1. More than that is overkill.
--
dwmw2
next prev parent reply other threads:[~2004-08-31 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 19:30 jffs2 file corruption Brian T
2004-08-30 19:40 ` Josh Boyer
2004-08-30 20:05 ` Brian T
2004-08-30 20:53 ` Thomas Gleixner
2004-08-30 21:19 ` Brian T
2004-08-30 21:19 ` Thomas Gleixner
2004-08-31 14:59 ` Brian T
2004-08-31 15:41 ` David Woodhouse
2004-08-31 17:08 ` Brian T
2004-08-31 17:11 ` David Woodhouse
2004-08-31 19:59 ` Brian T
2004-08-31 20:00 ` David Woodhouse [this message]
2004-09-01 15:30 ` Brian T
2004-08-31 20:01 ` Brian T
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=1093982409.6200.54.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=btuch@usa.net \
--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 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.