public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Vipin Malik <vipin@embeddedlinuxworks.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD Partition problems
Date: Tue, 6 Aug 2002 11:35:54 +0200	[thread overview]
Message-ID: <20020806093554.GA7162@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <5.1.0.14.0.20020805140501.00af1850@ns.webzsite.com>

On Mon, 5 August 2002 14:10:24 -0500, Vipin Malik wrote:
> Well, I think there is still a problem somewhere. Regardless of which 
> /dev/mtd<n> device is the actual physical partition (that was a good 
> academic discussion), JFFS2 never gets passed the /dev/mtd<n> device by me- 
> only the /dev/mtdblock<n> device.

I fail to see what was academic about that discussion. Is it academic,
if you pass /dev/hda1 (empty partition) or /dev/hda (whole disk with
root partition) to mke2fs? Try it and tell me again. :-)

> I can do a 'less -f /dev/mtdblock2' and see that's the partition that I 
> want to mount JFFS2 on (it's all formatted correctly). However, a 'mount -t 
> jffs2 /dev/mtdblock2 /mnt/flash' fails as JFFS2 sees a bunch of data to 
> whichever mtd device handle its been passed (by mtdblock2) and refuses to 
> mount as it cannot find any valid JFFS2 nodes there.

If it was formatted correctly, it should get mounted. But I have no
idea, what "it's all formatted correctly" or "JFFS2 sees a bunch of
data" means. Try doing a trivial format (eraseall /dev/mtd<n>) and
mount that. If that fails, show me that the partition has all 0xff and
the jffs2 messages and I will have a look. Until then, I consider this
to be pebkac.

Jörn

-- 
There's nothing better for promoting creativity in a medium than
making an audience feel "Hmm ­ I could do better than that!"
-- Douglas Adams in a slashdot interview

  reply	other threads:[~2002-08-06  9:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 21:59 MTD Partition problems Malik, Vipin [FRCO/HOU]
2002-08-03  9:46 ` Jörn Engel
2002-08-03 12:47   ` Vipin Malik
2002-08-03 14:10     ` Jörn Engel
2002-08-03 19:24       ` Vipin Malik
2002-08-03 23:50         ` Jörn Engel
2002-08-05 19:10           ` Vipin Malik
2002-08-06  9:35             ` Jörn Engel [this message]
2002-08-06 19:08           ` Vipin Malik
2002-08-05 10:35       ` David Woodhouse
2002-08-05 13:35         ` Disk blocks for long periods Joakim Tjernlund
2002-08-05 13:44           ` David Woodhouse
2002-08-05 13:59             ` Joakim Tjernlund
2002-08-05 14:12               ` David Woodhouse
2002-08-05 14:32                 ` Joakim Tjernlund
2002-08-05 14:42                   ` David Woodhouse
2002-08-05 21:45                     ` Jasmine Strong

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=20020806093554.GA7162@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vipin@embeddedlinuxworks.com \
    /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