All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Haynes <simon@baydel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Corruption.
Date: Tue, 24 Feb 2004 16:17:35 +0000	[thread overview]
Message-ID: <69D8404D0D5E@baydel.com> (raw)
In-Reply-To: <1077639264.7826.516.camel@hades.cambridge.redhat.com>

On Tuesday 24 Feb 2004 4:14 pm, David Woodhouse wrote:
> On Tue, 2004-02-24 at 15:47 +0000, Simon Haynes wrote:
> > I hacked fs/jffs2/super.c and fs/jffs2/super_v24.c. Only the v24 got
> > compiled. I guess this is because my kernel is 2.4.21.  I had to also
> > include ramdisk in the kernel as it was previously missing ? Does this
> > effect MTD ?
>
> No, it neither effects nor affects the MTD drivers.
>
> > This mounted rw.
>
> OK... now can you reproduce the same _problem_ that way?

My problem only occurs across reboots. As the ramdisk is not persistent 
storage how can I try and reproduce the problem. I have tried to reproduce 
the problem on mtd devices without rebooting and I have not managed to to 
this. 

Cheers 

SImon. 

  reply	other threads:[~2004-02-24 16:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 16:48 JFFS2 Corruption simon
2004-02-23 11:07 ` simon
2004-02-24  9:48   ` simon
2004-02-24 12:00     ` David Woodhouse
2004-02-24 12:54       ` Simon Haynes
2004-02-24 13:04       ` Simon Haynes
2004-02-24 13:40         ` Simon Haynes
2004-02-24 14:22           ` David Woodhouse
2004-02-24 14:25             ` Simon Haynes
2004-02-24 14:56               ` David Woodhouse
2004-02-24 14:58                 ` Simon Haynes
2004-02-24 15:35                   ` David Woodhouse
2004-02-24 15:47                     ` Simon Haynes
2004-02-24 16:14                       ` David Woodhouse
2004-02-24 16:17                         ` Simon Haynes [this message]
2004-02-24 16:51                           ` David Woodhouse
2004-02-24 17:05                             ` Simon Haynes
2004-02-24 18:05                               ` David Woodhouse
2004-02-24 18:04                                 ` Simon Haynes
2004-02-25  9:49                                 ` simon
2004-02-25 10:25                                   ` David Woodhouse
2004-02-26 11:08                                     ` Simon Haynes
2004-02-26 11:55                                       ` David Woodhouse
2004-03-03 15:31                                       ` David Woodhouse
2004-03-08 15:10                                         ` Simon Haynes
2004-03-09 15:33                                           ` Simon Haynes
2004-03-16 16:14                                             ` David Woodhouse
2004-03-19 10:37                                               ` Simon Haynes
2004-03-19 11:11                                                 ` David Woodhouse
2004-02-24 17:12                             ` Simon Haynes
2004-02-24 16:55                           ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 13:15 JFFS2 corruption Florian Schirmer
2004-02-08 10:37 ` David Woodhouse
2004-02-08 11:38   ` Florian Schirmer
2004-02-08 11:53     ` David Woodhouse
2004-02-08 17:02       ` Florian Schirmer
2004-02-08 17:13         ` David Woodhouse
2004-02-08 11: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=69D8404D0D5E@baydel.com \
    --to=simon@baydel.com \
    --cc=dwmw2@infradead.org \
    --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.