public inbox for linux-mtd@lists.infradead.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 13:40:05 +0000	[thread overview]
Message-ID: <69481CB84E71@baydel.com> (raw)
In-Reply-To: <6927194562DA@baydel.com>

On Tuesday 24 Feb 2004 1:04 pm, Simon Haynes wrote:
> On Tuesday 24 Feb 2004 12:54 pm, Simon Haynes wrote:
> > On Tuesday 24 Feb 2004 12:00 pm, David Woodhouse wrote:
> > > On Tue, 2004-02-24 at 09:48 +0000, simon@baydel.com wrote:
> > > > Comitted the sin of posting a reply with the reply text first, sorry.
> > >
> > > And this time you committed the sin of including _far_ more of the
> > > previous mail(s) than was necessary. But I'm not feeling cruel today so
> > > I'll not continue to ignore you :)
> > >
> > > > I have only managed to get this to fail if the jffs2 filesystem is
> > > > mounted as root. I do not seem to be able to get it to close and
> > > > unmount
> >
> > Thanks for the reply I am really struggling with this. I appreciate that
> > this stuff keeps you really busy and I will try to make it as easy for
> > you as I can.
>
> Ah,  I see the ro stuff is a kernel change. I will give it a go.
>

I don't understand. I changed the kernel to use the read only device. I 
expected this to work rw without caching but it does not. I have already 
tried mounting root ro via the caching mtd block and although my system does 
not fully start I can't see how I would get corruption ? 

I have looked at the mtdblock_ro code and it seems you allow writing if flag 
certain bits are set you allow writing. Do I need to set these somewhere ?

Cheers Simon.

  reply	other threads:[~2004-02-24 14:17 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 [this message]
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
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=69481CB84E71@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox