public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: Re: jffs2 file corruption
Date: Tue, 31 Aug 2004 09:59:02 -0500	[thread overview]
Message-ID: <07e301c48f6b$0e95fdc0$fd0ba8c0@briantpc> (raw)
In-Reply-To: 1093900751.16320.28.camel@thomas.tec.linutronix.de

[-- Attachment #1: Type: text/plain, Size: 3635 bytes --]


> Where's the problem ? The messages stop when the command is finished.
> Enable logging in minicom and you get all what you want. So the log
> contains your commands, but thats not too bad.

Attached is my zipped syslog. From bootup, I touched a file, and then echo'd
some chars into it.  Everthing looks fine, even the file.

[root@JBMgateway-60b root]# touch me
[root@JBMgateway-60b root]# echo "thisisatest" > me
[root@JBMgateway-60b root]# cat me
thisisatest
[root@JBMgateway-60b root]#


If I reboot, then the system is hosed, and needs to be reflashed :

cfi_cmdset_0001: Erase suspend on write enabled
SNAPGEAR: Intel flash device size = 16384K
Creating 6 MTD partitions on "SnapGear Intel":
0x00000000-0x000e0000 : "JBM kernel"
mtd: Giving out device 0 to JBM kernel
0x00100000-0x00fe0000 : "JBM filesystem"
mtd: Giving out device 1 to JBM filesystem
0x000e0000-0x00100000 : "JBM config"
mtd: Giving out device 2 to JBM config
0x00000000-0x01000000 : "JBM Intel"
mtd: Giving out device 3 to JBM Intel
0x00fe0000-0x01000000 : "JBM BIOS Config"
mtd: Giving out device 4 to JBM BIOS Config
0x00fe0000-0x01000000 : "JBM BIOS"
mtd: Giving out device 5 to JBM BIOS
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
Linux IP multicast router 0.06 plus PIM-SM
ip_conntrack version 2.1 (512 buckets, 4096 max) - 288 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
arp_tables: (C) 2002 David S. Miller
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Ethernet Bridge 008 for NET4.0
NET4: Linux IPX 0.47 for NET4.0
IPX Portions Copyright (c) 1995 Caldera, Inc.
IPX Portions Copyright (c) 2000, 2001 Conectiva, Inc.
Eep. Child "ttyS0" (ino #204) of dir ino #4 doesn't exist!
Eep. Child "ttyp0" (ino #225) of dir ino #4 doesn't exist!
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing unused kernel memory: 68k freed
jffs2_do_read_inode() on nonexistent ino 204
init started:  BusyBox v0.60.5 (2004.08.30-17:24+0000) multi-call binary
Bad inittab entry: ttyS0::respawn:/bin/getty 9600 -
  -- Device '/dev/ttyS0' not present.
jffs2_do_read_inode(): No data nodes found for ino #714
jffs2_do_read_inode(): But it has children so we fake some modes for it
Newly-erased block contained word 0x7f007f at offset 0x00dc0000
mke2fs 1.25 (20-Sep-2001)
Emptying and files in /mnt/ramfs/
Attempting to Make a RAM Filesystem on /mnt/ramfs/
mke2fs 1.25 (20-Sep-2001)
HOSTNAME set to JBMgateway-60b
Finding module dependencies:  [FAILED]
Loading JBM Feature Code Driver
Using /lib/modules/2.4.27/kernel/drivers/char/jbm_feature.o
JBM BRAM Found - Attempting to mount.
unable to open device '/dev/mtdblock6'.
unable to open device '/dev/mtdblock6'.
mount: Mounting /dev/mtdblock6 on /mnt/bram failed: No such device
Initializing BRAM - Mount Failed
mkfs.minix: /dev/mtdblock6: No such device
/etc/rc.d/rc.sysinit: /sbin/fsck.minix: Input/output error
/etc/rc.d/rc.sysinit: /sbin/fsck.minix: Input/output error
/etc/rc.d/rc.sysinit: mount: command not found
modprobe: modprobe: Can't open dependencies file
/lib/modules/2.4.27/modules.dep (No such file or directory)
Setting clock: Tue Aug 31 09:59:04 CDT 2004 Tue Aug 31 09:59:04 CDT 2004
[  OK  ]
Starting Cron:  [  OK  ]
**Runlevel is ALWAYS 3
**Remember this when using "chkconfig"
Using /lib/modules/2.4.27/kernel/drivers/char/jbmcoctl.o
/lib/modules/2.4.27/kernel/drivers/char/jbmcoctl.o: init_module: No such
device or address
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters






[-- Attachment #2: log.zip --]
[-- Type: application/octet-stream, Size: 20835 bytes --]

  reply	other threads:[~2004-08-31 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 19:30 jffs2 file corruption Brian T
2004-08-30 19:40 ` Josh Boyer
2004-08-30 20:05   ` Brian T
2004-08-30 20:53     ` Thomas Gleixner
2004-08-30 21:19       ` Brian T
2004-08-30 21:19         ` Thomas Gleixner
2004-08-31 14:59           ` Brian T [this message]
2004-08-31 15:41             ` David Woodhouse
2004-08-31 17:08               ` Brian T
2004-08-31 17:11                 ` David Woodhouse
2004-08-31 19:59                   ` Brian T
2004-08-31 20:00                     ` David Woodhouse
2004-09-01 15:30                       ` Brian T
2004-08-31 20:01                   ` Brian T

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='07e301c48f6b$0e95fdc0$fd0ba8c0@briantpc' \
    --to=btuch@usa.net \
    --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