All of lore.kernel.org
 help / color / mirror / Atom feed
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 18:11:51 +0100	[thread overview]
Message-ID: <1093972311.6200.47.camel@localhost.localdomain> (raw)
In-Reply-To: <080401c48f7d$253bda60$fd0ba8c0@briantpc>

On Tue, 2004-08-31 at 12:08 -0500, Brian T wrote:
> I'll try to get that done tomorrow.  Will take some time to setup remote
> syslog, boot, break it, turn off, dump the image, reboot, and dump the
> broken image.  Each image will probably be around 10MB compressed.  David, I
> can put the files on an FTP server and give you the link if you will have
> time to take a peek at them
> 
> Let me know what you want me to do.

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)

-- 
dwmw2

  reply	other threads:[~2004-08-31 17:11 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 [this message]
2004-08-31 19:59                   ` Brian T
2004-08-31 20:00                     ` David Woodhouse
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=1093972311.6200.47.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.