From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Nethra <nethra_gmit@yahoo.co.in>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: jffs2 file system on MPC8272ADS board
Date: Thu, 27 Sep 2007 23:01:54 +0400 [thread overview]
Message-ID: <20070927230154.4b761450@kernel.crashing.org> (raw)
In-Reply-To: <12900017.post@talk.nabble.com>
Hello Nethra,
On Wed, 26 Sep 2007 05:34:14 -0700 (PDT)
Nethra wrote:
>
>
> Hello ,
>
> >>
> >> hi everyone,
> >>
> >> I m using custom board similar to MPC8272ADS board...
> >>
> >> 1) For the first time it boots up properly in case if we overwrite any
> >> existing binaries using nfs mounted file system on the board, after
> >> rebooting it displays fallowing message...
> >>
> >> Further such events for this erase block will not be printed
> >> Eep. Child "null" (ino #1346) of dir ino #3 doesn't exist!
> >> Eep. Child "autocomm" (ino #463) of dir ino #461 doesn't exist!
> >> Eep. Child "calibration" (ino #464) of dir ino #461 doesn't exist!
> >> Eep. Child "coredsp_driver.ko" (ino #939) of dir ino #336 doesn't exist!
> >> Inode #1307 was a directory with children - removing those too...
> >> Inode #564 was a directory with children - removing those too...
> >> Inode #565 was a directory with children - removing those too...
> >> Inode #1112 was a directory with children - removing those too...
> >> Inode #1115 was a directory with children - removing those too...
> >> Inode #1118 was a directory with children - removing those too...
> >> Inode #1123 was a directory with children - removing those too...
> >>
> >> after this board boots up properly....but it not be having overwritten
> >> files
> >>
>
> >Have you created jffs2 file system on flash prior to mounting it?
>
> Yes I created jffs2 filesytem using mkfs.jffs2 prior to mounting and then I
> am over-writing some of the binaries. In case of overwrites from NFS after
> reboot
> I see the above errors & the binaries/directories gets deleted from the
> jffs2 partition.
>
> >> 3) when board is running properly in between it starts printing on
> >> console
> >> repeatedly...
> >>
>
> >Do the proper MTD partitions setup, erase the partition and create jffs2
> filesystem on it.
> >If after all those steps you're still getting output, that is prolly flakey
> flash.
>
> >> Header CRC failed on REF_PRISTINE node at 0x00638a6c: Read 0xffffffff,
> >> calculated 0x44660075
> >> Node totlen on flash (0xffffffff) != totlen from node ref (0x00000254)
> >> Header CRC failed on REF_PRISTINE node at 0x00638cc0: Read 0xffffffff,
> >> calculated 0x44660075
> [...]
> >> and
> >>
> >> file system is created using fallowing command..
> >>
> >> mkfs.jffs2 -r RFS_NEW/ -e 0x20000 -o /tftpboot/jffs2_img -b
> >>
> >I am recalling playing with the options upper also cured the jffs2 warnings
> (not as many as yours but anyway)
>
> The other options I am wondering about,
> -c, --cleanmarker=SIZE Size of cleanmarker (default 12)
> -n, --no-cleanmarkers Don't add a cleanmarker to every eraseblock
> cleanmaker size will it help the cause?
well, try to get rid of padding first.
are you sure about -e? please try
mkfs.jffs2 -e 128 -d ./myimage -b -o out.jffs2 instead.
--
Sincerely, Vitaly
prev parent reply other threads:[~2007-09-27 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 5:47 jffs2 file system on MPC8272ADS board Nethra
2007-09-25 16:22 ` Vitaly Bordug
2007-09-26 12:34 ` Nethra
2007-09-27 15:14 ` Detlev Zundel
2007-09-27 19:01 ` Vitaly Bordug [this message]
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=20070927230154.4b761450@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nethra_gmit@yahoo.co.in \
/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.