* jffs2 file corruption
@ 2004-08-30 19:30 Brian T
2004-08-30 19:40 ` Josh Boyer
0 siblings, 1 reply; 14+ messages in thread
From: Brian T @ 2004-08-30 19:30 UTC (permalink / raw)
To: linux-mtd
Trying to (still) update from 2.4.20 to 2.4.27 on an x86 embedded unit.
Made the kernel with CVS from 20040826 ( and added in the __ffs macro from
the previous thread ).
Running on a 486 with 16mb Intel flash, 128k size erase sectors. To create
the file system I run :
mkfs.jffs2 -o romfs.img -U -n -p -e0x2000 -d romfs/
Bootup seems fine, but I get a lot of file anomalies. I have a 24MB RAMFS on
/mnt/ramfs and then a sym link /mnt/ramfs -> /tmp . After bootup I get
wierd errors like :
[root@JBMgateway-60b /]# ls -al
drwxr-xr-x 15 root root 0 Aug 30 09:10 .
drwxr-xr-x 15 root root 0 Aug 30 09:10 ..
drwxr-xr-x 2 root root 0 Feb 21 2003 bin
drwxr-xr-x 2 root root 0 Aug 30 12:41 boot
drwxr-xr-x 4 root root 0 Aug 30 13:38 dev
drwxr-xr-x 23 root root 0 Aug 30 14:10 etc
drwxr-xr-x 4 root root 0 Aug 30 13:38 home
drwxr-xr-x 3 root root 0 Aug 30 09:10 lib
drwxr-xr-x 4 root root 0 Aug 30 09:10 mnt
dr-xr-xr-x 24 root root 0 Aug 30 09:09 proc
drwx------ 3 root root 0 Aug 30 14:13 root
drwxr-xr-x 2 root root 0 Aug 30 13:39 sbin
lrwxrwxrwx 1 root root 14 Aug 30 09:10 tmpls: ls:./tmp:
Input/output error
drwxr-xr-x 8 root root 0 Aug 30 12:41 usr
drwxr-xr-x 11 root root 1024 Aug 30 09:10 var
[root@JBMgateway-60b /]#
Modifying a simple test file seems fine, but then when rebootnig, here come
the CRC errors, and then the file system is unreadable.
jffs2_scan_inode_node(): CRC failed on node at 0x0085c83c: Read 0xffffffff,
calculated 0x3dd4adc1
jffs2_scan_dirent_node(): Node CRC failed on node at 0x0085c880: Read
0xffffffff, calculated 0x60506a80
jffs2_scan_inode_node(): CRC failed on node at 0x0085c8b0: Read 0xffffffff,
calculated 0x66cb4f63
jffs2_scan_dirent_node(): Node CRC failed on node at 0x0085c904: Read
0xffffffff, calculated 0x010d4523
jffs2_scan_inode_node(): CRC failed on node at 0x0085c930: Read 0xffffffff,
calculated 0xafde3a90
jffs2_scan_dirent_node(): Node CRC failed on node at 0x0085ca04: Read
0xffffffff, calculated 0x469dcd79
jffs2_scan_dirent_node(): Name CRC failed on node at 0x0085ca7c: Read
0xffffffff, calculated 0xeb3e1d4d
Name for which CRC failed is (now) 'modules.generic_string', ino #1100
jffs2_scan_dirent_node(): Node CRC failed on node at 0x0085cb00: Read
0xffffffff, calculated 0x1e774b92
jffs2_scan_dirent_node(): Name CRC failed on node at 0x0085cb7c: Read
0xffffffff, calculated 0xb7bf6d20
Name for which CRC failed is (now) 'modules.isapnpmap', ino #1102
jffs2_scan_dirent_node(): Name CRC failed on node at 0x0085cbfc: Read
0xffffffff, calculated 0xcea9e734
Name for which CRC failed is (now) 'modules.usbmap', ino #1103
jffs2_scan_dirent_node(): Name CRC failed on node at 0x0085cc78: Read
0x062b5a20, calculated 0x5ace6da0
Name for which CRC failed is (now) 'ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ', ino #1104
jffs2_scan_inode_node(): CRC failed on node at 0x0085ccb4: Read 0xffffffff,
calculated 0xf1cf28e5
jffs2_scan_inode_node(): CRC failed on node at 0x0085cea4: Read 0xe163b78c,
calculated 0x409744e1
jffs2_scan_inode_node(): CRC failed on node at 0x0085cf08: Read 0xf34fa9ec,
calculated 0x13bf9a28
jffs2_scan_inode_node(): CRC failed on node at 0x0085d098: Read 0xffffffff,
calculated 0x2da33634
jffs2_scan_inode_node(): CRC failed on node at 0x0085d15c: Read 0xffffffff,
calculated 0x6f47bf3e
jffs2_scan_inode_node(): CRC failed on node at 0x0085d21c: Read 0xffffffff,
calculated 0x54293253
jffs2_scan_inode_node(): CRC failed on node at 0x0085d280: Read 0xffffffff,
calculated 0x42184e2e
jffs2_scan_inode_node(): CRC failed on node at 0x0085d328: Read 0x5f9e29e9,
calculated 0xdd3e4daa
jffs2_scan_dirent_node(): Node CRC failed on node at 0x0085d36c: Read
0xffffffff, calculated 0x745f5ba5
jffs2_scan_dirent_node(): Name CRC failed on node at 0x0085d3dc: Read
0xffffffff, calculated 0x622d0693
Name for which CRC failed is (now) 'ÿÿÿÿÿÿÿ', ino #1106
jffs2_scan_inode_node(): CRC failed on node at 0x0085d40c: Read 0xfa3e5fb3,
calculated 0x5a961571
jffs2_scan_dirent_node(): Node CRC failed on node at 0x0085d540: Read
0xffffffff, calculated 0xcb60985b
jffs2_scan_inode_node(): CRC failed on node at 0x0085d578: Read 0xffffffff,
calculated 0x33e0776a
jffs2_scan_inode_node(): CRC failed on node at 0x0085d6bc: Read 0xffffffff,
calculated 0xf154fbed
jffs2_scan_inode_node(): CRC failed on node at 0x0085d758: Read 0xffffffff,
calculated 0x6e3afbab
jffs2_scan_inode_node(): CRC failed on node at 0x0085d7e4: Read 0xffffffff,
calculated 0x95e5c90a
jffs2_scan_inode_node(): CRC failed on node at 0x0085df34: Read 0xf1b2e00a,
calculated 0x7b22602f
jffs2_scan_dirent_node(): Name CRC failed on node at 0x0085e21c: Read
0xffffffff, calculated 0x44660075
Name for which CRC failed is (now) 'ÿÿÿÿÿÿÿÿ', ino #1108
jffs2_scan_inode_node(): CRC failed on node at 0x0085e24c: Read 0x8cf894c6,
calculated 0xbe9398cf
jffs2_scan_inode_node(): CRC failed on node at 0x0085e354: Read 0x5b92cae1,
calculated 0xc23ffe4d
jffs2_scan_inode_node(): CRC failed on node at 0x0085e44c: Read 0xde01eb00,
calculated 0x42630983
jffs2_scan_inode_node(): CRC failed on node at 0x0085e548: Read 0x74e71294,
calculated 0xa3d47e39
jffs2_scan_inode_node(): CRC failed on node at 0x0085e64c: Read 0xc3fdc1fb,
calculated 0x16337947
jffs2_scan_inode_node(): CRC failed on node at 0x0085e74c: Read 0x4445f7a7,
calculated 0x3c1b4125
jffs2_scan_inode_node(): CRC failed on node at 0x0085e84c: Read 0xd0435f78,
calculated 0x60f32d5a
jffs2_scan_inode_node(): CRC failed on node at 0x0085e948: Read 0x8da40476,
calculated 0x81445ae0
jffs2_scan_inode_node(): CRC failed on node at 0x0085ea4c: Read 0x773f1cdd,
calculated 0x34a35d9e
jffs2_scan_inode_node(): CRC failed on node at 0x0085eb48: Read 0xf58d6700,
calculated 0xd5142a24
jffs2_scan_inode_node(): CRC failed on node at 0x0085ec40: Read 0xffffffff,
calculated 0x7c62fbb8
jffs2_scan_inode_node(): CRC failed on node at 0x0085ed38: Read 0xffffffff,
calculated 0x7113a596
jffs2_scan_inode_node(): CRC failed on node at 0x0085ee44: Read 0xffffffff,
calculated 0x3905c1db
jffs2_scan_inode_node(): CRC failed on node at 0x0085ef3c: Read 0xffffffff,
calculated 0x0fa51510
jffs2_scan_inode_node(): CRC failed on node at 0x0085f038: Read 0xffffffff,
calculated 0x5f49a4bf
jffs2_scan_inode_node(): CRC failed on node at 0x0085f13c: Read 0xffffffff,
calculated 0x9cb17bc1
jffs2_scan_inode_node(): CRC failed on node at 0x0085f23c: Read 0xffffffff,
calculated 0x0cb7be77
jffs2_scan_inode_node(): CRC failed on node at 0x0085f334: Read 0xa3c1242f,
calculated 0x5f301f3b
jffs2_scan_inode_node(): CRC failed on node at 0x0085f42c: Read 0xffffffff,
calculated 0x258b8b28
jffs2_scan_inode_node(): CRC failed on node at 0x0085f524: Read 0x3557473f,
calculated 0x025dc0cf
jffs2_scan_inode_node(): CRC failed on node at 0x0085f624: Read 0xffffffff,
calculated 0x7c258869
jffs2_scan_inode_node(): CRC failed on node at 0x0085f720: Read 0xffffffff,
calculated 0x840cddf2
jffs2_scan_inode_node(): CRC failed on node at 0x0085f820: Read 0xffffffff,
calculated 0x369a3c9d
jffs2_scan_inode_node(): CRC failed on node at 0x0085f944: Read 0xffffffff,
calculated 0x20cde416
jffs2_scan_inode_node(): CRC failed on node at 0x0085fa44: Read 0xffffffff,
calculated 0x5eb5acb0
jffs2_scan_inode_node(): CRC failed on node at 0x0085fb48: Read 0xffffffff,
calculated 0xd1424c7a
jffs2_scan_inode_node(): CRC failed on node at 0x0085fc4c: Read 0x52529d72,
calculated 0x9bae91ae
jffs2_scan_inode_node(): CRC failed on node at 0x00a0000c: Read 0x7bb3e2bb,
calculated 0xef0ad820
jffs2_scan_inode_node(): CRC failed on node at 0x00a00298: Read 0xffffffff,
calculated 0x7c8b1ae1
jffs2_scan_inode_node(): CRC failed on node at 0x00a00538: Read 0xffffffff,
calculated 0xb8ddaf93
jffs2_scan_inode_node(): CRC failed on node at 0x00a00630: Read 0x275a9e11,
calculated 0x1142c36c
jffs2_scan_inode_node(): CRC failed on node at 0x00a00728: Read 0x5b33633d,
calculated 0x4e248036
jffs2_scan_inode_node(): CRC failed on node at 0x00a00820: Read 0xffffffff,
calculated 0xc0f196c7
jffs2_scan_inode_node(): CRC failed on node at 0x00a00918: Read 0xffffffff,
calculated 0x45847470
jffs2_scan_inode_node(): CRC failed on node at 0x00a00a1c: Read 0xffffffff,
calculated 0xd6e1f52b
jffs2_scan_inode_node(): CRC failed on node at 0x00a00b10: Read 0x5d017b89,
calculated 0x66dc119c
jffs2_scan_inode_node(): CRC failed on node at 0x00a00c04: Read 0xffffffff,
calculated 0xf6651b0d
jffs2_scan_inode_node(): CRC failed on node at 0x00a00d00: Read 0xffffffff,
calculated 0xa31ffaff
Empty flash at 0x00a00df8 ends at 0x00a00e4c
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00e4c:
0xb5a6 instead
Empty flash at 0x00a00e50 ends at 0x00a00f80
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f80:
0xa825 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f84:
0x5ad2 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f88:
0x736a instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f8c:
0x0a64 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f90:
0x6975 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f94:
0x1b7b instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f98:
0x3071 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00f9c:
0x8cf4 instead
Empty flash at 0x00a00fa0 ends at 0x00a00fe0
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a00fe0:
0x1e97 instead
Further such events for this erase block will not be printed
jffs2_scan_inode_node(): CRC failed on node at 0x00a00fec: Read 0x7ebe65cf,
calculated 0x71f34219
jffs2_scan_inode_node(): CRC failed on node at 0x00a010e8: Read 0x1b0229b4,
calculated 0x904435a3
jffs2_scan_inode_node(): CRC failed on node at 0x00a011e4: Read 0xffffffff,
calculated 0x2805ae98
Empty flash at 0x00a012e0 ends at 0x00a0132c
Empty flash at 0x00a01330 ends at 0x00a014e4
Empty flash at 0x00a014e8 ends at 0x00a0151c
Empty flash at 0x00a01520 ends at 0x00a01530
Empty flash at 0x00a01540 ends at 0x00a01560
Empty flash at 0x00a01580 ends at 0x00a015c0
Empty flash at 0x00a015e0 ends at 0x00a01620
Empty flash at 0x00a01640 ends at 0x00a01680
Empty flash at 0x00a016a0 ends at 0x00a016e0
Empty flash at 0x00a01700 ends at 0x00a01740
Empty flash at 0x00a01760 ends at 0x00a017a0
Empty flash at 0x00a017c0 ends at 0x00a01800
Empty flash at 0x00a01820 ends at 0x00a01840
jffs2_scan_inode_node(): CRC failed on node at 0x00a01840: Read 0x945362e5,
calculated 0x371f4e2a
Empty flash at 0x00a01b98 ends at 0x00a01ca0
Empty flash at 0x00a01cc0 ends at 0x00a01d00
Empty flash at 0x00a01d20 ends at 0x00a01d40
Empty flash at 0x00a01d60 ends at 0x00a01da0
Empty flash at 0x00a01dc0 ends at 0x00a01e00
Empty flash at 0x00a01e20 ends at 0x00a01e60
Empty flash at 0x00a01e80 ends at 0x00a01ea0
Empty flash at 0x00a01ec0 ends at 0x00a01ee0
Empty flash at 0x00a01f00 ends at 0x00a01f08
jffs2_scan_inode_node(): CRC failed on node at 0x00a01f08: Read 0x728a5c77,
calculated 0x81340cd5
jffs2_scan_inode_node(): CRC failed on node at 0x00a0228c: Read 0x5578d44f,
calculated 0x34d30bab
jffs2_scan_inode_node(): CRC failed on node at 0x00a025e0: Read 0xffffffff,
calculated 0xf7d74c5e
jffs2_scan_inode_node(): CRC failed on node at 0x00a026e0: Read 0xffffffff,
calculated 0xc8fd7401
jffs2_scan_inode_node(): CRC failed on node at 0x00a027ec: Read 0x3e74c680,
calculated 0x3f495e15
JFFS2: Erase block at 0x00a00000 is not formatted. It will be erased
Eep. Child "ttyS0" (ino #204) of dir ino #4 doesn't exist!
Eep. Child "libncurses.so.5" (ino #1098) of dir ino #7 doesn't exist!
Eep. Child "rc.sysinit" (ino #442) of dir ino #286 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() on nonexistent ino 442
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.sysinit: Input/output error
What other info would be needed to figure out what's wrong with this
picture?
Thanks,
-Brian
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-30 19:30 jffs2 file corruption Brian T
@ 2004-08-30 19:40 ` Josh Boyer
2004-08-30 20:05 ` Brian T
0 siblings, 1 reply; 14+ messages in thread
From: Josh Boyer @ 2004-08-30 19:40 UTC (permalink / raw)
To: Brian T; +Cc: linux-mtd
On Mon, 2004-08-30 at 14:30, Brian T wrote:
> Trying to (still) update from 2.4.20 to 2.4.27 on an x86 embedded unit.
> Made the kernel with CVS from 20040826 ( and added in the __ffs macro from
> the previous thread ).
>
> Running on a 486 with 16mb Intel flash, 128k size erase sectors. To create
> the file system I run :
>
> mkfs.jffs2 -o romfs.img -U -n -p -e0x2000 -d romfs/
128KiB is 0x20000 (131072), not 0x2000 (8192). Not sure if that was a
typo or not.
> What other info would be needed to figure out what's wrong with this
> picture?
Maybe try setting CONFIG_JFFS2_FS_DEBUG=1.
josh
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-30 19:40 ` Josh Boyer
@ 2004-08-30 20:05 ` Brian T
2004-08-30 20:53 ` Thomas Gleixner
0 siblings, 1 reply; 14+ messages in thread
From: Brian T @ 2004-08-30 20:05 UTC (permalink / raw)
To: linux-mtd
> >
> > mkfs.jffs2 -o romfs.img -U -n -p -e0x2000 -d romfs/
>
> 128KiB is 0x20000 (131072), not 0x2000 (8192). Not sure if that was a
> typo or not.
>
Yeah typo, sorry.
> > What other info would be needed to figure out what's wrong with this
> > picture?
>
> Maybe try setting CONFIG_JFFS2_FS_DEBUG=1.
Did that. My /var/ partition is a 512K RAMFS, and /var/log/messages rotates
after 200K. I will probably need to up that partition a bit and make the
log rotate higher to get more debug stuff.
-Brian
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-30 20:05 ` Brian T
@ 2004-08-30 20:53 ` Thomas Gleixner
2004-08-30 21:19 ` Brian T
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Gleixner @ 2004-08-30 20:53 UTC (permalink / raw)
To: Brian T; +Cc: linux-mtd
On Mon, 2004-08-30 at 22:05, Brian T wrote:
> Did that. My /var/ partition is a 512K RAMFS, and /var/log/messages rotates
> after 200K. I will probably need to up that partition a bit and make the
> log rotate higher to get more debug stuff.
>
Use a serial console and not syslogd. Else you will have messed debug
output which is not helpful at all
tglx
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-30 20:53 ` Thomas Gleixner
@ 2004-08-30 21:19 ` Brian T
2004-08-30 21:19 ` Thomas Gleixner
0 siblings, 1 reply; 14+ messages in thread
From: Brian T @ 2004-08-30 21:19 UTC (permalink / raw)
To: tglx; +Cc: linux-mtd
> >
> Use a serial console and not syslogd. Else you will have messed debug
> output which is not helpful at all
>
Bummer. Then I am in a catch-22. Console is the main login for these
units.
No video, keyboard, mouse. Only console and Ethernet/Cell Modem/Modem/etc.
-Brian
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-30 21:19 ` Brian T
@ 2004-08-30 21:19 ` Thomas Gleixner
2004-08-31 14:59 ` Brian T
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Gleixner @ 2004-08-30 21:19 UTC (permalink / raw)
To: Brian T; +Cc: linux-mtd
On Mon, 2004-08-30 at 23:19, Brian T wrote:
> > >
> > Use a serial console and not syslogd. Else you will have messed debug
> > output which is not helpful at all
> Bummer. Then I am in a catch-22. Console is the main login for these
> units.
> No video, keyboard, mouse. Only console and Ethernet/Cell Modem/Modem/etc.
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.
tglx
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-30 21:19 ` Thomas Gleixner
@ 2004-08-31 14:59 ` Brian T
2004-08-31 15:41 ` David Woodhouse
0 siblings, 1 reply; 14+ messages in thread
From: Brian T @ 2004-08-31 14:59 UTC (permalink / raw)
To: linux-mtd
[-- 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 --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-31 14:59 ` Brian T
@ 2004-08-31 15:41 ` David Woodhouse
2004-08-31 17:08 ` Brian T
0 siblings, 1 reply; 14+ messages in thread
From: David Woodhouse @ 2004-08-31 15:41 UTC (permalink / raw)
To: Brian T; +Cc: linux-mtd
On Tue, 2004-08-31 at 09:59 -0500, Brian T wrote:
> 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.
Logging via syslog is too lossy to be useful. Please obtain messages
over a serial console or possibly netconsole if that's reliable enough.
You need even the KERN_DEBUG messages which are absent from your syslog,
too.
I need to see what it said while it wrote the new file, then what it
said while remounting the offending file system. If you can take a
snapshot of the flash after writing the file and turning the machine
off, but before remounting it, that would be useful too.
--
dwmw2
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-31 15:41 ` David Woodhouse
@ 2004-08-31 17:08 ` Brian T
2004-08-31 17:11 ` David Woodhouse
0 siblings, 1 reply; 14+ messages in thread
From: Brian T @ 2004-08-31 17:08 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-mtd
>
> Logging via syslog is too lossy to be useful. Please obtain messages
> over a serial console or possibly netconsole if that's reliable enough.
>
> You need even the KERN_DEBUG messages which are absent from your syslog,
> too.
>
> I need to see what it said while it wrote the new file, then what it
> said while remounting the offending file system. If you can take a
> snapshot of the flash after writing the file and turning the machine
> off, but before remounting it, that would be useful too.
>
Ok,
I'll try to get that done tomorrow. Will take some time to setup remote
syslog, boot, break it, turn off, dump the image, reboot, and dump the
broken image. Each image will probably be around 10MB compressed. David, I
can put the files on an FTP server and give you the link if you will have
time to take a peek at them
Let me know what you want me to do.
-Brian
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
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:01 ` Brian T
0 siblings, 2 replies; 14+ messages in thread
From: David Woodhouse @ 2004-08-31 17:11 UTC (permalink / raw)
To: Brian T; +Cc: linux-mtd
On Tue, 2004-08-31 at 12:08 -0500, Brian T wrote:
> I'll try to get that done tomorrow. Will take some time to setup remote
> syslog, boot, break it, turn off, dump the image, reboot, and dump the
> broken image. Each image will probably be around 10MB compressed. David, I
> can put the files on an FTP server and give you the link if you will have
> time to take a peek at them
>
> Let me know what you want me to do.
Putting them up for download is probably better than mailing them to the
list -- yes.
Make sure that your log includes KERN_DEBUG messages and isn't lossy.
Remote syslog isn't necessarily good enough -- a serial console
certainly is.
Let me know the inode number of the test file you created too (ls -i me)
--
dwmw2
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-31 17:11 ` David Woodhouse
@ 2004-08-31 19:59 ` Brian T
2004-08-31 20:00 ` David Woodhouse
2004-08-31 20:01 ` Brian T
1 sibling, 1 reply; 14+ messages in thread
From: Brian T @ 2004-08-31 19:59 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-mtd
> Putting them up for download is probably better than mailing them to the
> list -- yes.
>
> Make sure that your log includes KERN_DEBUG messages and isn't lossy.
> Remote syslog isn't necessarily good enough -- a serial console
> certainly is.
>
> Let me know the inode number of the test file you created too (ls -i me)
>
I got console logging on, and will run some tests. I'll send you a priv
email where to get the files from.
With KERN_DEBUG (all options) on, I don't see anything extra in the syslog.
Should there be?
-Brian
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-31 19:59 ` Brian T
@ 2004-08-31 20:00 ` David Woodhouse
2004-09-01 15:30 ` Brian T
0 siblings, 1 reply; 14+ messages in thread
From: David Woodhouse @ 2004-08-31 20:00 UTC (permalink / raw)
To: Brian T; +Cc: linux-mtd
On Tue, 2004-08-31 at 14:59 -0500, Brian T wrote:
> > Putting them up for download is probably better than mailing them to the
> > list -- yes.
> >
> > Make sure that your log includes KERN_DEBUG messages and isn't lossy.
> > Remote syslog isn't necessarily good enough -- a serial console
> > certainly is.
> >
> > Let me know the inode number of the test file you created too (ls -i me)
> >
>
> I got console logging on, and will run some tests. I'll send you a priv
> email where to get the files from.
>
> With KERN_DEBUG (all options) on, I don't see anything extra in the syslog.
> Should there be?
man syslogd.conf
syslog doesn't log messages at KERN_DEBUG by default. But syslog is too
lossy anyway. Use a serial console.
Use CONFIG_JFFS2_FS_DEBUG=1. More than that is overkill.
--
dwmw2
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-31 20:00 ` David Woodhouse
@ 2004-09-01 15:30 ` Brian T
0 siblings, 0 replies; 14+ messages in thread
From: Brian T @ 2004-09-01 15:30 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-mtd
> > With KERN_DEBUG (all options) on, I don't see anything extra in the
syslog.
> > Should there be?
>
> man syslogd.conf
>
> syslog doesn't log messages at KERN_DEBUG by default. But syslog is too
> lossy anyway. Use a serial console.
>
> Use CONFIG_JFFS2_FS_DEBUG=1. More than that is overkill.
>
David, I sent you 2 log files. I have an image untainted (before bootup).
I flashed the unit to allow it to boot so I could then pull the image off
through the bootloader, but it failed to start init and completely come up
this time. I have the console log. Do you want a link to an image that has
booted successfully, or *this* image that failed? Or both?
-Brian
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: jffs2 file corruption
2004-08-31 17:11 ` David Woodhouse
2004-08-31 19:59 ` Brian T
@ 2004-08-31 20:01 ` Brian T
1 sibling, 0 replies; 14+ messages in thread
From: Brian T @ 2004-08-31 20:01 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-mtd
> Make sure that your log includes KERN_DEBUG messages and isn't lossy.
> Remote syslog isn't necessarily good enough -- a serial console
> certainly is.
>
> Let me know the inode number of the test file you created too (ls -i me)
>
sorry forgot to ask... MTD debugging on? JFFS2 DEBUG=1? 3?
-Brian
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2004-09-01 15:30 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox