All of lore.kernel.org
 help / color / mirror / Atom feed
* UBIFS trouble
@ 2009-07-09 17:55 Daniel Mack
  2009-07-09 18:00 ` Adrian Hunter
  0 siblings, 1 reply; 7+ messages in thread
From: Daniel Mack @ 2009-07-09 17:55 UTC (permalink / raw)
  To: Adrian Hunter, Artem Bityutskiy; +Cc: linux-mtd

(re-posting with the correct linux-mtd ML address. Sorry)

Hey,

I'm running the latest git snapshot of the Linux kernel on a PXA3xx
based board. Connected to the PXA3xx is a 128MiB Nymonix NAND chip
which I've set to enourmously relaxed timings for now (factor 2 on all
values).

'nandtest -p 100 /dev/mtd3' runs for hours without any trouble and
succeeds every test. However, when I create an UBIFS on that mtd and
start bonnie to stress-test the filesystem layer, I keep on seeing
messages like this:

[  382.374993] UBIFS error (pid 1133): ubifs_read_node: bad node at LEB 58:106008
[  382.382178] UBIFS error (pid 1133): do_readpage: cannot read page 38693 of inode 66, error -22
[  382.390968] timed out writing command
[  382.394830] UBI error: ubi_io_read: error -74 while reading 76 bytes from PEB 245:105736, read 76 bytes
[  382.404186] UBIFS error (pid 1135): try_read_node: cannot read node type 1 from LEB 68:101640, error -74
[  382.413698] UBIFS error (pid 1135): ubifs_read_node: bad node type (255 but expected 1)
[  382.421718] UBIFS error (pid 1135): ubifs_read_node: bad node at LEB 68:101640
[  382.428941] UBIFS error (pid 1135): do_readpage: cannot read page 53753 of inode 66, error -22
[  648.164435] UBIFS error (pid 1138): ubifs_read_node: bad node type (70 but expected 9)
[  648.172317] UBIFS error (pid 1138): ubifs_read_node: bad node at LEB 110:112896
[  648.179677] UBIFS error (pid 1138): do_readpage: cannot read page 19432 of inode 32838, error -22
[  648.188650] timed out writing command
[  648.192379] UBI error: ubi_io_read: error -74 while reading 81 bytes from PEB 738:80616, read 81 bytes
[  648.201732] UBIFS error (pid 1136): try_read_node: cannot read node type 1 from LEB 72:76520, error -74
[  648.211137] UBIFS error (pid 1136): ubifs_read_node: bad node type (255 but expected 1)
[  648.219115] UBIFS error (pid 1136): ubifs_read_node: bad node at LEB 72:76520
[  648.226231] UBIFS error (pid 1136): do_readpage: cannot read page 26131 of inode 32838, error -22

Once in awhile only and not frequently, but it still scares me. Is there
anything I should consider? Any more information I can provide for
further debugging?

(btw - it happens with the timings found in the datasheet as well, I
just extended them to exclude timing issues as culprit.)

I'd like to use that filesystem in a device, but I need to get it to a
more stable point for that.

Many thanks,
Daniel

^ permalink raw reply	[flat|nested] 7+ messages in thread
* UBIFS trouble
@ 2016-11-29 11:02 Juergen Borleis
  2016-11-29 14:04 ` Juergen Borleis
  0 siblings, 1 reply; 7+ messages in thread
From: Juergen Borleis @ 2016-11-29 11:02 UTC (permalink / raw)
  To: barebox

Hi,

with an older barebox (2015.08) I can see in my NOR:

barebox@board: ls -l /mnt/nor0.file-system.ubi.rootfs/boot/
-rw-r--r--    1686716 System.map-4.1.0-none-board
-rw-r--r--      67615 config-4.1.0-none-board
lrwxrwxrwx         30 initrd.img -> initrd.img-4.1.0-none-board
-rw-r--r--    2180972 initrd.img-4.1.0-none-board
lrwxrwxrwx         67 oftree -> ../usr/lib/linux-image-4.1.0-none-board/omap3-mfr-board.dtb
-rw-r--r--    3375248 vmlinuz-4.1.0-none-board
-rw-r--r--    3426056 vmlinuz-ptx-board
lrwxrwxrwx         15 zImage -> vmlinuz-ptx-board

A 4.1 Linux kernel sees this filesystem in the same manner:

root@board:~# ll /boot/
total 10496
-rw-r--r-- 1 root root 1686716 Jul 11  2016 System.map-4.1.0-none-board
-rw-r--r-- 1 root root   67615 Jul 11  2016 config-4.1.0-none-board
lrwxrwxrwx 1 root root      30 Oct 24  2016 initrd.img -> initrd.img-4.1.0-none-board
-rw-r--r-- 1 root root 2180972 Oct 24  2016 initrd.img-4.1.0-none-board
lrwxrwxrwx 1 root root      67 Oct 24  2016 oftree -> ../usr/lib/linux-image-4.1.0-none-board/omap3-mfr-board.dtb
-rw-r--r-- 1 root root 3375248 Jul 11  2016 vmlinuz-4.1.0-none-board
-rw-r--r-- 1 root root 3426056 Oct  1  2016 vmlinuz-ptx-board
lrwxrwxrwx 1 root root      15 Oct  1  2016 zImage -> vmlinuz-ptx-board

A fresh barebox (2016.11.0) sees this filesystem differently:

barebox@board:/ ls -l /mnt/nor0.file-system.ubi.rootfs/boot/
-rw-r--r--        1686716 System.map-4.1.0-none-board
-rw-r--r--          67615 config-4.1.0-none-board
-rw-r--r--        2180972 initrd.img
-rw-r--r--        2180972 initrd.img-4.1.0-none-board
/mnt/nor0.file-system.ubi.rootfs/boot//oftree: No such file or directory
-rw-r--r--        3375248 vmlinuz-4.1.0-none-board
-rw-r--r--        3426056 vmlinuz-ptx-board
-rw-r--r--        3426056 zImage

Any idea?

jb

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-12-07 20:50 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-09 17:55 UBIFS trouble Daniel Mack
2009-07-09 18:00 ` Adrian Hunter
2009-07-09 18:11   ` Daniel Mack
2009-07-09 18:56     ` Daniel Mack
  -- strict thread matches above, loose matches on Subject: below --
2016-11-29 11:02 Juergen Borleis
2016-11-29 14:04 ` Juergen Borleis
2016-12-07 20:50   ` Sascha Hauer

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.