UBIFS crash (was Re: Problems with mtd_oobtest)

UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Dear all,

>> Now, I'll do some intentional power cuts, and when the problem
>> appears, I'll post a kernel log here.
>
> Please, be aware of the unstable bits issue which not one dares to
> resolve in UBIFS, but many people yelled...
>
> http://www.linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits

Thanks for the link, I'll check it.

Now, I did what I said, and after some power crashes, I get:
==============================================================================
[    1.576000] UBIFS: recovery needed
[    1.584000] UBIFS error (pid 1): check_lpt_crc: invalid crc in LPT
node: crc f382 calc f342
[    1.588000] [<c002ba14>] (unwind_backtrace+0x0/0xe0) from
[<c0124604>] (check_lpt_crc+0x78/0x90)
[    1.592000] [<c0124604>] (check_lpt_crc+0x78/0x90) from
[<c01246e4>] (ubifs_unpack_nnode+0xc8/0xd8)
[    1.596000] [<c01246e4>] (ubifs_unpack_nnode+0xc8/0xd8) from
[<c01248e8>] (ubifs_read_nnode+0xc8/0x188)
[    1.600000] [<c01248e8>] (ubifs_read_nnode+0xc8/0x188) from
[<c01249c4>] (ubifs_get_nnode+0x1c/0x30)
[    1.604000] [<c01249c4>] (ubifs_get_nnode+0x1c/0x30) from
[<c01257d8>] (ubifs_lpt_lookup_dirty+0x6c/0x258)
[    1.608000] [<c01257d8>] (ubifs_lpt_lookup_dirty+0x6c/0x258) from
[<c0119d1c>] (ubifs_replay_journal+0x28/0x14d0)
[    1.612000] [<c0119d1c>] (ubifs_replay_journal+0x28/0x14d0) from
[<c010ec9c>] (ubifs_fill_super+0xc08/0x12b8)
[    1.616000] [<c010ec9c>] (ubifs_fill_super+0xc08/0x12b8) from
[<c0110314>] (ubifs_get_sb+0x1f4/0x258)
[    1.620000] [<c0110314>] (ubifs_get_sb+0x1f4/0x258) from
[<c008ae14>] (vfs_kern_mount+0x50/0xd0)
[    1.624000] [<c008ae14>] (vfs_kern_mount+0x50/0xd0) from
[<c008aed8>] (do_kern_mount+0x34/0xd8)
[    1.628000] [<c008aed8>] (do_kern_mount+0x34/0xd8) from
[<c009e618>] (do_mount+0x5e4/0x648)
[    1.632000] [<c009e618>] (do_mount+0x5e4/0x648) from [<c009e700>]
(sys_mount+0x84/0xc4)
[    1.636000] [<c009e700>] (sys_mount+0x84/0xc4) from [<c0008ba4>]
(do_mount_root+0x20/0xb4)
[    1.640000] [<c0008ba4>] (do_mount_root+0x20/0xb4) from
[<c0008e24>] (mount_block_root+0xe8/0x20c)
[    1.644000] [<c0008e24>] (mount_block_root+0xe8/0x20c) from
[<c00090d8>] (prepare_namespace+0x8c/0x1c8)
[    1.648000] [<c00090d8>] (prepare_namespace+0x8c/0x1c8) from
[<c000874c>] (kernel_init+0xd4/0x10c)
[    1.652000] [<c000874c>] (kernel_init+0xd4/0x10c) from [<c0026df0>]
(kernel_thread_exit+0x0/0x8)
[    1.656000] UBIFS error (pid 1): ubifs_read_nnode: error -22
reading nnode at 8:6651
[    1.660000] [<c002ba14>] (unwind_backtrace+0x0/0xe0) from
[<c0124984>] (ubifs_read_nnode+0x164/0x188)
[    1.664000] [<c0124984>] (ubifs_read_nnode+0x164/0x188) from
[<c01249c4>] (ubifs_get_nnode+0x1c/0x30)
[    1.668000] [<c01249c4>] (ubifs_get_nnode+0x1c/0x30) from
[<c01257d8>] (ubifs_lpt_lookup_dirty+0x6c/0x258)
[    1.672000] [<c01257d8>] (ubifs_lpt_lookup_dirty+0x6c/0x258) from
[<c0119d1c>] (ubifs_replay_journal+0x28/0x14d0)
[    1.676000] [<c0119d1c>] (ubifs_replay_journal+0x28/0x14d0) from
[<c010ec9c>] (ubifs_fill_super+0xc08/0x12b8)
[    1.680000] [<c010ec9c>] (ubifs_fill_super+0xc08/0x12b8) from
[<c0110314>] (ubifs_get_sb+0x1f4/0x258)
[    1.684000] [<c0110314>] (ubifs_get_sb+0x1f4/0x258) from
[<c008ae14>] (vfs_kern_mount+0x50/0xd0)
[    1.688000] [<c008ae14>] (vfs_kern_mount+0x50/0xd0) from
[<c008aed8>] (do_kern_mount+0x34/0xd8)
[    1.692000] [<c008aed8>] (do_kern_mount+0x34/0xd8) from
[<c009e618>] (do_mount+0x5e4/0x648)
[    1.696000] [<c009e618>] (do_mount+0x5e4/0x648) from [<c009e700>]
(sys_mount+0x84/0xc4)
[    1.700000] [<c009e700>] (sys_mount+0x84/0xc4) from [<c0008ba4>]
(do_mount_root+0x20/0xb4)
[    1.704000] [<c0008ba4>] (do_mount_root+0x20/0xb4) from
[<c0008e24>] (mount_block_root+0xe8/0x20c)
[    1.708000] [<c0008e24>] (mount_block_root+0xe8/0x20c) from
[<c00090d8>] (prepare_namespace+0x8c/0x1c8)
[    1.712000] [<c00090d8>] (prepare_namespace+0x8c/0x1c8) from
[<c000874c>] (kernel_init+0xd4/0x10c)
[    1.716000] [<c000874c>] (kernel_init+0xd4/0x10c) from [<c0026df0>]
(kernel_thread_exit+0x0/0x8)
[    1.724000] List of all partitions:
[    1.728000] 1f00             128 mtdblock0 (driver?)
[    1.732000] 1f01          109824 mtdblock1 (driver?)
[    1.736000] No filesystem could mount root, tried:  ubifs
[    1.740000] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0)

==============================================================================

I re-flashed the unit, rebooted several time and:
==============================================================================
[    1.576000] UBIFS error (pid 1): ubifs_scan: garbage
[    1.616000] UBI: scrubbed PEB 3 (LEB 0:1), data moved to PEB 2
[    1.644000] UBIFS error (pid 1): ubifs_recover_master_node: failed
to recover master node
==============================================================================

Again, with the same result:
==============================================================================
[    1.608000] UBIFS: recovery needed
[    1.752000] UBIFS error (pid 1): ubifs_check_node: bad magic
0x6104531, expected 0x6101831
[    1.756000] UBIFS error (pid 1): ubifs_check_node: bad node at LEB 140:81848
[    1.760000] [<c002ba14>] (unwind_backtrace+0x0/0xe0) from
[<c01122f4>] (ubifs_check_node+0x264/0x2a8)
[    1.764000] [<c01122f4>] (ubifs_check_node+0x264/0x2a8) from
[<c0112c80>] (ubifs_read_node+0x184/0x274)
[    1.772000] [<c0112c80>] (ubifs_read_node+0x184/0x274) from
[<c012da9c>] (ubifs_load_znode+0xc0/0x50c)
[    1.776000] [<c012da9c>] (ubifs_load_znode+0xc0/0x50c) from
[<c0116288>] (ubifs_lookup_level0+0x104/0x1c8)
[    1.780000] [<c0116288>] (ubifs_lookup_level0+0x104/0x1c8) from
[<c01165e0>] (ubifs_tnc_next_ent+0x74/0x178)
[    1.784000] [<c01165e0>] (ubifs_tnc_next_ent+0x74/0x178) from
[<c0117e1c>] (ubifs_tnc_remove_ino+0x50/0x180)
[    1.788000] [<c0117e1c>] (ubifs_tnc_remove_ino+0x50/0x180) from
[<c011acac>] (ubifs_replay_journal+0xfb8/0x14d0)
[    1.792000] [<c011acac>] (ubifs_replay_journal+0xfb8/0x14d0) from
[<c010ec9c>] (ubifs_fill_super+0xc08/0x12b8)
[    1.796000] [<c010ec9c>] (ubifs_fill_super+0xc08/0x12b8) from
[<c0110314>] (ubifs_get_sb+0x1f4/0x258)
[    1.800000] [<c0110314>] (ubifs_get_sb+0x1f4/0x258) from
[<c008ae14>] (vfs_kern_mount+0x50/0xd0)
[    1.804000] [<c008ae14>] (vfs_kern_mount+0x50/0xd0) from
[<c008aed8>] (do_kern_mount+0x34/0xd8)
[    1.808000] [<c008aed8>] (do_kern_mount+0x34/0xd8) from
[<c009e618>] (do_mount+0x5e4/0x648)
[    1.812000] [<c009e618>] (do_mount+0x5e4/0x648) from [<c009e700>]
(sys_mount+0x84/0xc4)
[    1.816000] [<c009e700>] (sys_mount+0x84/0xc4) from [<c0008ba4>]
(do_mount_root+0x20/0xb4)
[    1.820000] [<c0008ba4>] (do_mount_root+0x20/0xb4) from
[<c0008e24>] (mount_block_root+0xe8/0x20c)
[    1.824000] [<c0008e24>] (mount_block_root+0xe8/0x20c) from
[<c00090d8>] (prepare_namespace+0x8c/0x1c8)
[    1.828000] [<c00090d8>] (prepare_namespace+0x8c/0x1c8) from
[<c000874c>] (kernel_init+0xd4/0x10c)
[    1.832000] [<c000874c>] (kernel_init+0xd4/0x10c) from [<c0026df0>]
(kernel_thread_exit+0x0/0x8)
[    1.836000] UBIFS error (pid 1): ubifs_read_node: expected node type 9
[    1.844000] VFS: Cannot open root device "ubi0:ubi_rootfs" or
unknown-block(0,0)
[    1.848000] Please append a correct "root=" boot option; here are
the available partitions:
[    1.852000] 1f00             128 mtdblock0 (driver?)
[    1.856000] 1f01          109824 mtdblock1 (driver?)
[    1.860000] b300         7842816 mmcblk0 driver: mmcblk
[    1.868000]   b301         7838720 mmcblk0p1
[    1.872000] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0)
==============================================================================


Please note, that I have several similar devices and majority of them
don't have this problem.
The one I am using now, seems to crash with different errors.
Is this the symptom I could expect from the problem mentioned in the
link you provided?
Any other problem?

Thank you and Best Regards,
Matej Kupljen

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Artem Bityutskiy]

On Sat, 2012-03-10 at 07:07 +0100, Matej Kupljen wrote:
> Please note, that I have several similar devices and majority of them
> don't have this problem.
> The one I am using now, seems to crash with different errors.
> Is this the symptom I could expect from the problem mentioned in the
> link you provided?
> Any other problem?

Do you see any issues if you have no power cuts, or these things only
happen as a result of power cuts?

-- 
Best Regards,
Artem Bityutskiy

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Dear, Artem,

>> Please note, that I have several similar devices and majority of them
>> don't have this problem.
>> The one I am using now, seems to crash with different errors.
>> Is this the symptom I could expect from the problem mentioned in the
>> link you provided?
>> Any other problem?
>
> Do you see any issues if you have no power cuts, or these things only
> happen as a result of power cuts?

I'll try to reproduce the problem, by doing clean reboots and will get
back to you.

Thank you and Best Regards,
Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Dear, Artem,

>> Do you see any issues if you have no power cuts, or these things only
>> happen as a result of power cuts?
>
> I'll try to reproduce the problem, by doing clean reboots and will get
> back to you.

I tried to do a clean reboots, and today, when I turned on the device,
the UBIFS was mounted O.K., but then during init, I got the following error:

===========================================================================
[   26.164000] UBIFS error (pid 965): ubifs_read_node: bad node type
(255 but expected 0)
[   26.168000] UBIFS error (pid 965): ubifs_read_node: bad node at LEB
149:4416, LEB mapping status 1
[   26.176000] [<c002ba14>] (unwind_backtrace+0x0/0xe0) from
[<c0112d3c>] (ubifs_read_node+0x240/0x274)
[   26.180000] [<c0112d3c>] (ubifs_read_node+0x240/0x274) from
[<c012d94c>] (ubifs_tnc_read_node+0x50/0xe0)
[   26.184000] [<c012d94c>] (ubifs_tnc_read_node+0x50/0xe0) from
[<c0117130>] (ubifs_tnc_locate+0x134/0x17c)
[   26.188000] [<c0117130>] (ubifs_tnc_locate+0x134/0x17c) from
[<c010d950>] (ubifs_iget+0x6c/0x7b0)
[   26.192000] [<c010d950>] (ubifs_iget+0x6c/0x7b0) from [<c010c988>]
(ubifs_lookup+0x130/0x1d4)
[   26.196000] [<c010c988>] (ubifs_lookup+0x130/0x1d4) from
[<c0090898>] (__lookup_hash+0x110/0x130)
[   26.204000] [<c0090898>] (__lookup_hash+0x110/0x130) from
[<c00936b4>] (do_filp_open+0x200/0x8e4)
[   26.208000] [<c00936b4>] (do_filp_open+0x200/0x8e4) from
[<c008728c>] (do_sys_open+0x5c/0x114)
[   26.212000] [<c008728c>] (do_sys_open+0x5c/0x114) from [<c0025e20>]
(ret_fast_syscall+0x0/0x28)
[   26.216000] UBIFS error (pid 965): ubifs_iget: failed to read inode
1841, error -22
[   26.220000] UBIFS error (pid 965): ubifs_lookup: dead directory
entry 'updated.log', error -22
===========================================================================

However, I can still login and do a reboot, and when the board is
rebooted, I noticed this
in the boot log:

===========================================================================
[    0.836000] UBI error: check_corruption: PEB 160 contains corrupted
VID header, and the data does not contain all 0xFF, thin
[    1.216000] UBI error: check_what_we_have: 1 PEBs are corrupted and preserved
[    1.220000] Corrupted PEBs are: 160
[    1.224000] UBI: max. sequence number:       41
[    1.248000] UBI warning: print_rsvd_warning: cannot reserve enough
PEBs for bad PEB handling, reserved 7, need 8
[    1.252000] UBI warning: print_rsvd_warning: 1 PEBs are corrupted
and not used
===========================================================================

If I login the FS is mounted as RO. If I remount it in RW and try to
do a sync, I get:

===========================================================================
# sync
[  193.176000] UBIFS error (pid 369): make_reservation: cannot reserve
160 bytes in jhead 1, error -30
[  193.180000] UBIFS error (pid 369): ubifs_write_inode: can't write
inode 1855, error -30
[  193.196000] UBIFS error (pid 2886): do_commit: commit failed, error -30
===========================================================================

What could be the cause of such many errors in FS?
I am really running out of ideas, how to solve this, so any hint would
be appreciated.

Thank you and Best Regards,
Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Artem Bityutskiy]

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

On Tue, 2012-03-13 at 07:20 +0100, Matej Kupljen wrote:
> 
> What could be the cause of such many errors in FS?
> I am really running out of ideas, how to solve this, so any hint would
> be appreciated. 

This looks like non-UBI/UBIFS issue but more like issue with your flash
driver or HW. Start stress-testing the driver. Try MTD running mtd tests
over night.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Dear Artem,

>> What could be the cause of such many errors in FS?
>> I am really running out of ideas, how to solve this, so any hint would
>> be appreciated.
>
> This looks like non-UBI/UBIFS issue but more like issue with your flash
> driver or HW. Start stress-testing the driver. Try MTD running mtd tests
> over night.

O.K.
I already tried that, but only the mtd_oobtest failed.

Which tests should I run? All of them or maybe just mtd_stresstest?

Do I need to format the NAND?
I'll boot it with rootfs on SD card and try the stresstest.

Thanks and Best Regards,
Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Artem Bityutskiy]

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

On Tue, 2012-03-13 at 08:32 +0100, Matej Kupljen wrote:
> Dear Artem,
> 
> >> What could be the cause of such many errors in FS?
> >> I am really running out of ideas, how to solve this, so any hint would
> >> be appreciated.
> >
> > This looks like non-UBI/UBIFS issue but more like issue with your flash
> > driver or HW. Start stress-testing the driver. Try MTD running mtd tests
> > over night.
> 
> O.K.
> I already tried that, but only the mtd_oobtest failed.
> 
> Which tests should I run? All of them or maybe just mtd_stresstest?
> 
> Do I need to format the NAND?
> I'll boot it with rootfs on SD card and try the stresstest.

I think the mtd_torture test would also be a good one to run for a day
of 2.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Dear Artem,

>> Which tests should I run? All of them or maybe just mtd_stresstest?
>>

I sent you the results yesterday, with no errors.

> I think the mtd_torture test would also be a good one to run for a day
> of 2.

Here is the first results of the mtd_tourturetest:

[84703.428000] mtd_torturetest: 00010240 erase cycles done, took
2054461 milliseconds (2054 seconds)
[86757.800000] mtd_torturetest: 00010752 erase cycles done, took
2054365 milliseconds (2054 seconds)
[88812.120000] mtd_torturetest: 00011264 erase cycles done, took
2054319 milliseconds (2054 seconds)
[90866.352000] mtd_torturetest: 00011776 erase cycles done, took
2054229 milliseconds (2054 seconds)
[92920.496000] mtd_torturetest: 00012288 erase cycles done, took
2054137 milliseconds (2054 seconds)
[94974.508000] mtd_torturetest: 00012800 erase cycles done, took
2054008 milliseconds (2054 seconds)

As far as I can see, there are no errors yet.
Should I continue with this, or should I try something else?

Thank you and Best Regards,
Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Artem Bityutskiy]

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

On Wed, 2012-03-14 at 11:01 +0100, Matej Kupljen wrote:
> Here is the first results of the mtd_tourturetest:
> 
> [84703.428000] mtd_torturetest: 00010240 erase cycles done, took
> 2054461 milliseconds (2054 seconds)
> [86757.800000] mtd_torturetest: 00010752 erase cycles done, took
> 2054365 milliseconds (2054 seconds)
> [88812.120000] mtd_torturetest: 00011264 erase cycles done, took
> 2054319 milliseconds (2054 seconds)
> [90866.352000] mtd_torturetest: 00011776 erase cycles done, took
> 2054229 milliseconds (2054 seconds)
> [92920.496000] mtd_torturetest: 00012288 erase cycles done, took
> 2054137 milliseconds (2054 seconds)
> [94974.508000] mtd_torturetest: 00012800 erase cycles done, took
> 2054008 milliseconds (2054 seconds)

Well, it is still good to run it for few days.

But then I would try to do UBIFS testing in some limited environment to
exclude a possibility of some process writing directly to /dev/mtd and
corrupting data. E.g., testing it in a minimal shell.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Artem,

>> [94974.508000] mtd_torturetest: 00012800 erase cycles done, took
>> 2054008 milliseconds (2054 seconds)
>
> Well, it is still good to run it for few days.

I'll leave it running.

> But then I would try to do UBIFS testing in some limited environment to
> exclude a possibility of some process writing directly to /dev/mtd and
> corrupting data. E.g., testing it in a minimal shell.

What do you mean by that?
Still boot it from MMC, but then mount the UBIFS on some different
point and start testing? Which tests to do?

Thanks,
Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Artem Bityutskiy]

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

On Wed, 2012-03-14 at 13:55 +0100, Matej Kupljen wrote:
> What do you mean by that?
> Still boot it from MMC, but then mount the UBIFS on some different
> point and start testing? 

I guess I meant to somehow make sure that UBIFS exclusively owns the mtd
device and no one or nothing accesses it.

But I really do not know - the issues you report do not look like UBIFS
issues - the data on the flash is corrupted somehow - dunno how. There
are billions hypothetical reasons. It may be that your DRAM has a
problem, or DMA, or whatever. You can try to disable various parts of SW
(drivers, user-space apps) and see if it helps, and may be somehow find
what triggers the issue.

> Which tests to do?

Well, you can try the ones you used, or the fsstress test from the LTP
project, or I'd recommend to try the integck test from mtd-utils.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Dear Artem,

> I guess I meant to somehow make sure that UBIFS exclusively owns the mtd
> device and no one or nothing accesses it.

Thanks for all the suggestions, I guess I'll start with them now, because
my device has been tortured for 3 days with result:

[179113.412000] mtd_torturetest: 00033792 erase cycles done, took
2051108 milliseconds (2051 seconds)
[181164.576000] mtd_torturetest: 00034304 erase cycles done, took
2051160 milliseconds (2051 seconds)
[183215.724000] mtd_torturetest: 00034816 erase cycles done, took
2051143 milliseconds (2051 seconds)
[185266.832000] mtd_torturetest: 00035328 erase cycles done, took
2051102 milliseconds (2051 seconds)
[187317.844000] mtd_torturetest: 00035840 erase cycles done, took
2051006 milliseconds (2051 seconds)
[189368.464000] mtd_torturetest: 00036352 erase cycles done, took
2050615 milliseconds (2050 seconds)
[191419.440000] mtd_torturetest: 00036864 erase cycles done, took
2050974 milliseconds (2050 seconds)

I'll let you know if I find what caused all the problems.

Thank you again,
Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

Dear Artem,

> Well, you can try the ones you used, or the fsstress test from the LTP
> project, or I'd recommend to try the integck test from mtd-utils.

I finally found some time again to do the tests and cross compiled latest
mtd-utils form git. I booted form SD card, mounted the UBIFS and tried
to run integck, as you suggested. But here is what I get:

# ./integck /mnt/card/
integck: error!: cannot find file-system info
integck: error!: condition '0' failed in get_tested_fs_info() at integck.c:2942
integck: error 0 (Success)

Any known error?

Thanks and Best Regards,
Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Artem Bityutskiy]

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

On Thu, 2012-03-22 at 13:17 +0100, Matej Kupljen wrote:
> Dear Artem,
> 
> > Well, you can try the ones you used, or the fsstress test from the LTP
> > project, or I'd recommend to try the integck test from mtd-utils.
> 
> I finally found some time again to do the tests and cross compiled latest
> mtd-utils form git. I booted form SD card, mounted the UBIFS and tried
> to run integck, as you suggested. But here is what I get:
> 
> # ./integck /mnt/card/
> integck: error!: cannot find file-system info
> integck: error!: condition '0' failed in get_tested_fs_info() at integck.c:2942
> integck: error 0 (Success)
> 
> Any known error?

Well, you can always use gdb and look what's going on. I do not think
you'll get _that_ level of support on this forum. But most probably this
is because /mnt/card is not a ubifs file-system.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Matej Kupljen]

To all,

after reading the posts on the mailing list, with similar problems,  I
believe that
Artem was right already in the beginning where he suggested that I am
experiencing
"unstable bit" issue.

If you look at the kernel log, the dump of the empty space, clearly
shows one bit-flip,
where the first word is read as 0xfffffffd, instead of 0xffffffff.

So, at the moment no solution?

Thanks and best regards,
Matej


>>> # ./integck /mnt/card/
>>> integck: error!: cannot find file-system info
>>> integck: error!: condition '0' failed in get_tested_fs_info() at integck.c:2942
>>> integck: error 0 (Success)
>>>
>>> Any known error?
>>
>> Well, you can always use gdb and look what's going on. I do not think
>> you'll get _that_ level of support on this forum. But most probably this
>> is because /mnt/card is not a ubifs file-system.
>
> Yes, sorry for that to bother you with such question, but I just though maybe
> it has a simple answer.
> However, I managed to run the test now over the night and throughout the
> day I got the following error:
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
> integck: write 3581 bytes, offset 7209, file 984122 (line 903)
> integck: write 9 bytes, offset 94835, file 815280 (line 903)
> integck: creating dir
> /media/card/integck_test_dir_3350/ruhftdazbgbtlgruqmabfpgyfakxrpffgpsirpoqihsvcghbylinte)
> integck: write 42 bytes, offset 3, file 114936 (line 903)
> integck: creating file /media/card/integck_test_dir_3350/922415/757218
> (line 640)
> integck: write 963 bytes, offset 2631628, fileintegck: creating file
> /media/card/integck_test_dir_3350/936581 )
> integck: write 92490 bytes, offset 15525383, file 766624 (line 903)
> [22575.864000] UBIFS error (pid 3350): ubifs_scan: corrupt empty space
> at LEB 277:128602
> [22575.868000] UBIFS error (pid 3350): ubifs_scanned_corruption:
> corruption at LEB 277:128602
> [22575.872000] UBIFS error (pid 3350): ubifs_scanned_corruption:
> fir[22575.904000] UBIFS warning (pid 3350): u7
> [22575.908000] [<c002ba14>] (unwind_backtrace+0x0/0xe0) from
> [<c011e2b4>] (ubifs_garbage_collect+0x31c/0x378)
> [22575.912000] [<c011e2b4>] (ubifs_garbage_col9578>] (vfs_write+0xb0/0x15c)
> [22575.944000] [<c0089578>] (vfs_write+0xb0/0x15c) from [<c0089a54>]
> (sys_write+0x3c/0x68)
> [22575.948000] [<c0089a54>] (sys_write+0x3c/0x68) from [<c0025e20>]
> (ret_fast_syscall+0x0/0x28)
> [22575.952000] UBIFS error (pid 3721): make_reser[22576.008000] UBIFS
> error (pid 3721): make_reservation: cann0
> [22576.012000] UBIFS error (pid 3721): do_writepage: cannot write page
> 0 of inode 16664, error -30
> [22576.024000] UBIFS error (pid 3721): make_res UBIFS error (pid
> 3721): do_writepage: cannot write page 1259 o0
> [22576.076000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.084000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode page 164 of inode 17964, error -30
> [22576.136000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.140000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 17989, error -30
> [22576.152000] UBIFS error (pid 3_write_inode: can't write inode
> 17388, error -30
> [22576.188000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.192000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 18070, error -30
> [22576.204000] UBIFS[22576.240000] UBIFS error (pid 3721):
> make_reservation: cannot reserve 4144 bytes in jhea0
> [22576.244000] UBIFS error (pid 3721): do_writepage: cannot write page
> 3007 of inode 17993, error -30
> [22576.256000] UBIFS error (pid 3721): make_re9, error -30
> integck: failed to write 32768 bytes to offset 15544320 of file 766624
> (line 927, error 30 (Read-only file sys)
> [22576.304000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.308000] UBIFS error (pi[22576.428000] UBIFS: un-mount UBI
> device 0, volume 0
> [22576.592000] UBIFS: recovery needed
> [22577.772000] UBIFS error (pid 3350): ubifs_scan: corrupt empty space
> at LEB 277:128602
> [22577.776000] UBIFS error (pid 3350): ubifs_scanned_corruption:
> corruption at LEB 277:128602
> [22577.780000] UBIFS error (pid 3350): ubifs_scanned_corruption: first 422:3200
> integck: error 117 (Structure needs cleaning)
> ./integck[0x9adc]
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Here is the kernel log:
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
> [20914.720000] device: 'ubifs_0_0': device_create_release
> [20914.728000] device: 'ubifs_0_0': device_add
> [20914.728000] PM: Adding info for No Bus:ubifs_0_0
> [20914.920000] UBIFS: mounted UBI device 0, volume 0, name "ubi_rootfs"
> [20914.924000] UBIFS: file system size:   107218944 bytes (104706 KiB,
> 102 MiB, 831 LEBs)
> [20914.928000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8
> MiB, 71 LEBs)
> [20914.932000] UBIFS: media format:       w4/r0 (latest is w4/r0)
> [20914.936000] UBIFS: default compressor: lzo
> [20914.940000] UBIFS: reserved for root:  0 bytes (0 KiB)
> [21043.920000] UBIFS: un-mount UBI device 0, volume 0
> [21043.964000] device: 'ubifs_0_0': device_unregister
> [21043.964000] PM: Removing info for No Bus:ubifs_0_0
> [21043.964000] device: 'ubifs_0_0': device_create_release
> [21043.972000] device: 'ubifs_0_0': device_add
> [21043.972000] PM: Adding info for No Bus:ubifs_0_0
> [21044.184000] UBIFS: mounted UBI device 0, volume 0, name "ubi_rootfs"
> [21044.188000] UBIFS: mounted read-only
> [21044.192000] UBIFS: file system size:   107218944 bytes (104706 KiB,
> 102 MiB, 831 LEBs)
> [21044.196000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8
> MiB, 71 LEBs)
> [21044.200000] UBIFS: media format:       w4/r0 (latest is w4/r0)
> [21044.204000] UBIFS: default compressor: lzo
> [21044.208000] UBIFS: reserved for root:  0 bytes (0 KiB)
> [21346.300000] UBIFS: un-mount UBI device 0, volume 0
> [21346.340000] device: 'ubifs_0_0': device_unregister
> [21346.340000] PM: Removing info for No Bus:ubifs_0_0
> [21346.340000] device: 'ubifs_0_0': device_create_release
> [21346.348000] device: 'ubifs_0_0': device_add
> [21346.348000] PM: Adding info for No Bus:ubifs_0_0
> [21346.572000] UBIFS: mounted UBI device 0, volume 0, name "ubi_rootfs"
> [21346.576000] UBIFS: file system size:   107218944 bytes (104706 KiB,
> 102 MiB, 831 LEBs)
> [21346.580000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8
> MiB, 71 LEBs)
> [21346.584000] UBIFS: media format:       w4/r0 (latest is w4/r0)
> [21346.592000] UBIFS: default compressor: lzo
> [21346.596000] UBIFS: reserved for root:  0 bytes (0 KiB)
> [21580.356000] UBI: scrubbed PEB 8 (LEB 0:755), data moved to PEB 243
> [21833.916000] UBIFS: un-mount UBI device 0, volume 0
> [21833.960000] device: 'ubifs_0_0': device_unregister
> [21833.960000] PM: Removing info for No Bus:ubifs_0_0
> [21833.964000] device: 'ubifs_0_0': device_create_release
> [21833.972000] device: 'ubifs_0_0': device_add
> [21833.972000] PM: Adding info for No Bus:ubifs_0_0
> [21834.192000] UBIFS: mounted UBI device 0, volume 0, name "ubi_rootfs"
> [21834.196000] UBIFS: mounted read-only
> [21834.200000] UBIFS: file system size:   107218944 bytes (104706 KiB,
> 102 MiB, 831 LEBs)
> [21834.204000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8
> MiB, 71 LEBs)
> [21834.208000] UBIFS: media format:       w4/r0 (latest is w4/r0)
> [21834.212000] UBIFS: default compressor: lzo
> [21834.216000] UBIFS: reserved for root:  0 bytes (0 KiB)
> [22037.008000] UBIFS: un-mount UBI device 0, volume 0
> [22037.060000] device: 'ubifs_0_0': device_unregister
> [22037.060000] PM: Removing info for No Bus:ubifs_0_0
> [22037.060000] device: 'ubifs_0_0': device_create_release
> [22037.068000] device: 'ubifs_0_0': device_add
> [22037.068000] PM: Adding info for No Bus:ubifs_0_0
> [22037.240000] UBIFS: mounted UBI device 0, volume 0, name "ubi_rootfs"
> [22037.244000] UBIFS: mounted read-only
> [22037.248000] UBIFS: file system size:   107218944 bytes (104706 KiB,
> 102 MiB, 831 LEBs)
> [22037.252000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8
> MiB, 71 LEBs)
> [22037.256000] UBIFS: media format:       w4/r0 (latest is w4/r0)
> [22037.260000] UBIFS: default compressor: lzo
> [22037.264000] UBIFS: reserved for root:  0 bytes (0 KiB)
> [22163.020000] UBIFS: un-mount UBI device 0, volume 0
> [22163.064000] device: 'ubifs_0_0': device_unregister
> [22163.064000] PM: Removing info for No Bus:ubifs_0_0
> [22163.064000] device: 'ubifs_0_0': device_create_release
> [22163.072000] device: 'ubifs_0_0': device_add
> [22163.072000] PM: Adding info for No Bus:ubifs_0_0
> [22163.264000] UBIFS: mounted UBI device 0, volume 0, name "ubi_rootfs"
> [22163.268000] UBIFS: mounted read-only
> [22163.272000] UBIFS: file system size:   107218944 bytes (104706 KiB,
> 102 MiB, 831 LEBs)
> [22163.276000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8
> MiB, 71 LEBs)
> [22163.280000] UBIFS: media format:       w4/r0 (latest is w4/r0)
> [22163.284000] UBIFS: default compressor: lzo
> [22163.288000] UBIFS: reserved for root:  0 bytes (0 KiB)
> [22371.004000] UBI: scrubbed PEB 662 (LEB 0:482), data moved to PEB 634
> [22573.076000] UBI: scrubbed PEB 416 (LEB 0:518), data moved to PEB 634
> [22575.864000] UBIFS error (pid 3350): ubifs_scan: corrupt empty space
> at LEB 277:128602
> [22575.868000] UBIFS error (pid 3350): ubifs_scanned_corruption:
> corruption at LEB 277:128602
> [22575.872000] UBIFS error (pid 3350): ubifs_scanned_corruption: first
> 422 bytes from LEB 277:128602
> [22575.876000] 00000000: fffffffd ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 00000020: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 00000040: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 00000060: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 00000080: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 000000a0: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 000000c0: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 000000e0: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 00000100: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.876000] 00000120: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.880000] 00000140: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.880000] 00000160: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.880000] 00000180: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22575.880000] 000001a0: ff ff ff ff ff ff
>                                       .
> [22575.880000] UBIFS error (pid 3350): ubifs_scan: LEB 277 scanning failed
> [22575.904000] UBIFS warning (pid 3350): ubifs_ro_mode: switched to
> read-only mode, error -117
> [22575.908000] [<c002ba14>] (unwind_backtrace+0x0/0xe0) from
> [<c011e2b4>] (ubifs_garbage_collect+0x31c/0x378)
> [22575.912000] [<c011e2b4>] (ubifs_garbage_collect+0x31c/0x378) from
> [<c0120614>] (ubifs_budget_space+0x45c/0x)
> [22575.916000] [<c0120614>] (ubifs_budget_space+0x45c/0x594) from
> [<c010a818>] (ubifs_write_begin+0x394/0x524)
> [22575.920000] [<c010a818>] (ubifs_write_begin+0x394/0x524) from
> [<c006769c>] (generic_file_buffered_write+0xd)
> [22575.924000] [<c006769c>] (generic_file_buffered_write+0xdc/0x21c)
> from [<c0068b3c>] (__generic_file_aio_wri)
> [22575.928000] [<c0068b3c>] (__generic_file_aio_write+0x404/0x450)
> from [<c0068bec>] (generic_file_aio_write+0)
> [22575.932000] [<c0068bec>] (generic_file_aio_write+0x64/0xc4) from
> [<c0108f44>] (ubifs_aio_write+0x180/0x198)
> [22575.936000] [<c0108f44>] (ubifs_aio_write+0x180/0x198) from
> [<c0088d04>] (do_sync_write+0x98/0xe4)
> [22575.940000] [<c0088d04>] (do_sync_write+0x98/0xe4) from
> [<c0089578>] (vfs_write+0xb0/0x15c)
> [22575.944000] [<c0089578>] (vfs_write+0xb0/0x15c) from [<c0089a54>]
> (sys_write+0x3c/0x68)
> [22575.948000] [<c0089a54>] (sys_write+0x3c/0x68) from [<c0025e20>]
> (ret_fast_syscall+0x0/0x28)
> [22575.952000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22575.956000] UBIFS error (pid 3721): do_writepage: cannot write page
> 3006 of inode 17993, error -30
> [22575.964000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22575.968000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 17993, error -30
> [22575.980000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22575.984000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 18348, error -30
> [22576.008000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.012000] UBIFS error (pid 3721): do_writepage: cannot write page
> 0 of inode 16664, error -30
> [22576.024000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.028000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 16664, error -30
> [22576.040000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.044000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 12822, error -30
> [22576.052000] UBIFS error (pid 3350): ubifs_budget_space: cannot
> budget space, error -117
> [22576.064000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 146 bytes in jhead 2, error -30
> [22576.068000] UBIFS error (pid 3721): do_writepage: cannot write page
> 1259 of inode 17504, error -30
> [22576.076000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.084000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 17504, error -30
> [22576.092000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.096000] UBIFS error (pid 3721): do_writepage: cannot write page
> 411 of inode 17239, error -30
> [22576.104000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.108000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 17239, error -30
> [22576.120000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.124000] UBIFS error (pid 3721): do_writepage: cannot write page
> 164 of inode 17964, error -30
> [22576.136000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.140000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 17989, error -30
> [22576.152000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.156000] UBIFS error (pid 3721): do_writepage: cannot write page
> 213 of inode 18394, error -30
> [22576.168000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.172000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 18394, error -30
> [22576.176000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.180000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 17388, error -30
> [22576.188000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.192000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 18070, error -30
> [22576.204000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.208000] UBIFS error (pid 3721): do_writepage: cannot write page
> 28 of inode 17755, error -30
> [22576.212000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.216000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 17755, error -30
> [22576.224000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 160 bytes in jhead 1, error -30
> [22576.228000] UBIFS error (pid 3721): ubifs_write_inode: can't write
> inode 18088, error -30
> [22576.240000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.244000] UBIFS error (pid 3721): do_writepage: cannot write page
> 3007 of inode 17993, error -30
> [22576.256000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.260000] UBIFS error (pid 3721): do_writepage: cannot write page
> 10 of inode 18348, error -30
> [22576.268000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.272000] UBIFS error (pid 3721): do_writepage: cannot write page
> 2325 of inode 17504, error -30
> [22576.284000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.288000] UBIFS error (pid 3721): do_writepage: cannot write page
> 412 of inode 17239, error -30
> [22576.304000] UBIFS error (pid 3721): make_reservation: cannot
> reserve 4144 bytes in jhead 2, error -30
> [22576.308000] UBIFS error (pid 3721): do_writepage: cannot write page
> 165 of inode 17964, error -30
> [22576.428000] UBIFS: un-mount UBI device 0, volume 0
> [22576.476000] device: 'ubifs_0_0': device_unregister
> [22576.476000] PM: Removing info for No Bus:ubifs_0_0
> [22576.476000] device: 'ubifs_0_0': device_create_release
> [22576.484000] device: 'ubifs_0_0': device_add
> [22576.484000] PM: Adding info for No Bus:ubifs_0_0
> [22576.592000] UBIFS: recovery needed
> [22577.772000] UBIFS error (pid 3350): ubifs_scan: corrupt empty space
> at LEB 277:128602
> [22577.776000] UBIFS error (pid 3350): ubifs_scanned_corruption:
> corruption at LEB 277:128602
> [22577.780000] UBIFS error (pid 3350): ubifs_scanned_corruption: first
> 422 bytes from LEB 277:128602
> [22577.784000] 00000000: fffffffd ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 00000020: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 00000040: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 00000060: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 00000080: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 000000a0: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 000000c0: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 000000e0: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 00000100: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.784000] 00000120: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.788000] 00000140: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.788000] 00000160: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.788000] 00000180: ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffffffff ffffffff  .............
> [22577.788000] 000001a0: ff ff ff ff ff ff
>                                       .
> [22577.788000] UBIFS error (pid 3350): ubifs_scan: LEB 277 scanning failed
> [22577.792000] UBIFS error (pid 3350): ubifs_rcvry_gc_commit: GC
> failed, error -117
> [22577.832000] device: 'ubifs_0_0': device_unregister
> [22577.832000] PM: Removing info for No Bus:ubifs_0_0
> [22577.832000] device: 'ubifs_0_0': device_create_release
> root@obu4g:~/mtd-utils/tests/fs-tests/integrity#
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Is this log of any help for you?
> Should I send anything else?
>
> Thank you and Best Regards,
> Matej

Re: UBIFS crash (was Re: Problems with mtd_oobtest)

[Artem Bityutskiy]

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

On Sat, 2012-03-24 at 08:22 +0100, Matej Kupljen wrote:
> To all,
> 
> after reading the posts on the mailing list, with similar problems,  I
> believe that
> Artem was right already in the beginning where he suggested that I am
> experiencing
> "unstable bit" issue.
> 
> If you look at the kernel log, the dump of the empty space, clearly
> shows one bit-flip,
> where the first word is read as 0xfffffffd, instead of 0xffffffff.

The unstable bits issue is related to unclean reboots. AFAIU, you
observe problems when you do not have power cuts at all. This means you
have some issues in your driver/HW level. Did you check if your driver
corrects bit-flips in empty space?

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]