public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Catherine Smith" <catherine@arrows.demon.co.uk>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>,
	"John" <john@arrows.demon.co.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: OneNAND - Cannot mount jffs2 partition
Date: Sun, 13 Aug 2006 18:45:12 +0100	[thread overview]
Message-ID: <000e01c6bf00$3acdd130$c9fea8c0@Catherine> (raw)
In-Reply-To: 44DF16CC.3070708@yandex.ru

Thanks Artem.


> John wrote:
>> Questions:
>>   Is this a suitable pair of commands?
>>    $ flash_eraseall -j /dev/mtd5
>>    $ mount -t jffs2 /dev/mtdblock5 /mnt/onenand
> Yeah, I believe this is the right commands and should work.
>
>
>>   What is the likely underlying cause of the error message
>>       "Cowardly refusing to erase blocks on filesystem with
>>        no valid JFFS2 nodes"
> Hmm, JFFS2 is complaining that you feed it with a flash which is neither 
> empty nor contains a valid JFFS2 FS image.
>
> Try to avoid using -j and see what happens. You also may try to enable 
> JFFS2's debugging prints.
>
If I don't use the -j, it seems to work, though with a few warnings.
For example:
  $ flash_eraseall /dev/mtd5
  Eraseing 64 Kibyte @ 7f0000 -- 99 % complete
  $ mount -t jffs2 /dev/mtdblock5 /mnt/onenand
  Eep. no valid nodes for ino #1

Then I can create files in /mnt/onenand, and copy them around or calculate a 
few signatures. All is well.
Once, when I tried to mount after a power cycle, it said:
  jffs2_get_inode_nodes(): CRC failed on node at 0x002dd7c8: Read 
0xffffffff, calculated 0x20f0e445

Are these warnings, the Eep and the CRC failure, typical and harmless,
or should I take a keen interest?

>
> -- 
> Best Regards,
> Artem B. Bityutskiy,
> St.-Petersburg, Russia.
>
Regards,
John Smith
Lancashire, England 

  reply	other threads:[~2006-08-13 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13 10:24 OneNAND - Cannot mount jffs2 partition John
2006-08-13 12:10 ` Artem B. Bityutskiy
2006-08-13 17:45   ` Catherine Smith [this message]
2006-08-14 15:03     ` Artem B. Bityutskiy

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='000e01c6bf00$3acdd130$c9fea8c0@Catherine' \
    --to=catherine@arrows.demon.co.uk \
    --cc=dedekind@yandex.ru \
    --cc=john@arrows.demon.co.uk \
    --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