All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Eirik Aanonsen <eaa@wprmedical.com>
Cc: kernel@avr32linux.org, linux-mtd <linux-mtd@lists.infradead.org>
Subject: RE: UBIFS error CRC calculation on avr32 CPU
Date: Tue, 02 Dec 2008 17:15:33 +0200	[thread overview]
Message-ID: <1228230933.13686.8.camel@sauron> (raw)
In-Reply-To: <2DE39384A09B744FA1E53FD4BF78D430535E42@dware1013.doorway.loc>

On Tue, 2008-12-02 at 13:59 +0100, Eirik Aanonsen wrote:
> Here is the result from the actual move:
> ----------------------------------------
> 
> /mnt/slave # mv wpr_004.wfp ../master/
> UBIFS error (pid 529): ubifs_check_node: bad CRC: calculated 0x7dc26ea1, read 0x3f225006
> UBIFS error (pid 529): ubifs_check_node: bad node at LEB 184:236208
> Call trace:
>  [<90010694>] dump_stack+0x18/0x20
>  [<c0a5cde8>] ubifs_check_node+0x210/0x23c [ubifs]
>  [<c0a5cfe6>] ubifs_read_node+0x1d2/0x2d8 [ubifs]
>  [<c0a776bc>] ubifs_tnc_read_node+0x70/0x170 [ubifs]
>  [<c0a609a2>] ubifs_tnc_lookup+0x8a/0xb0 [ubifs]
>  [<c0a54c64>] do_readpage+0x1c8/0x434 [ubifs]
>  [<c0a54edc>] ubifs_readpage+0xc/0x18 [ubifs]
>  [<900352a4>] generic_file_aio_read+0x2dc/0x47c
>  [<9004b794>] do_sync_read+0x88/0xb4
>  [<9004bb4c>] vfs_read+0x62/0x8e
>  [<9004bcf2>] sys_read+0x2a/0x48
>  [<9000c132>] syscall_return+0x0/0x12
> 
> UBIFS error (pid 529): ubifs_read_node: expected node type 1
> UBIFS error (pid 529): do_readpage: cannot read page 1074 of inode 34246, error -117
> mv: read error: Input/output error
> /mnt/slave #
> 

It looks like you indeed have corrupted data. Where the 'wpr_004.wfp'
file comes from? You wrote it previously? Or you used mkfs.ubifs?

> UBIFS warning (pid 500): mount_ubifs: 'LZO' compressor is set by superblock, but not compiled in

Hmm. Why you do not enable LZO compressor? How did you
create your file-system?

Also, did you try to enable UBIFS and UBI extra self-checks? Please,
try. Things will become very slow then, though, but this may give
some useful information.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2008-12-02 15:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01  3:49 [ARM] pxa: explicit #include <mach/dma.h> in various drivers Eric Miao
2008-12-01 12:33 ` UBIFS error CRC calculation on avr32 CPU Eirik Aanonsen
2008-12-02  8:44   ` Artem Bityutskiy
2008-12-02 12:59     ` Eirik Aanonsen
2008-12-02 15:15       ` Artem Bityutskiy [this message]
2008-12-03  7:55         ` Eirik Aanonsen
2008-12-03  9:25           ` Artem Bityutskiy
2008-12-05 10:46             ` Eirik Aanonsen
2008-12-05 10:58               ` Artem Bityutskiy

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=1228230933.13686.8.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=eaa@wprmedical.com \
    --cc=kernel@avr32linux.org \
    --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 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.