From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jon Ringle <jon@ringle.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Fail to mount ubifs
Date: Tue, 12 Jan 2010 23:33:06 +0200 [thread overview]
Message-ID: <1263331986.3445.7.camel@localhost.localdomain> (raw)
In-Reply-To: <152584231001111620i6b397f43n49733caa8f92f472@mail.gmail.com>
On Mon, 2010-01-11 at 19:20 -0500, Jon Ringle wrote:
> I should be able to mount an empty ubi volume as ubifs right?
> But I get this on a freshly made volume:
> UBIFS error (pid 1493): check_lpt_crc: invalid crc in LPT node: crc
> cbcb calc cbfb
Yes.
>
> I'm not sure what to try now...
>
> Jon
>
> (initramfs) ubinfo -a
> UBI version: 1
> Count of UBI devices: 1
> UBI control device major/minor: 10:60
> Present UBI devices: ubi0
>
> ubi0
> Volumes count: 2
> Logical eraseblock size: 130944 bytes, f KiB
> Total amount of logical eraseblocks: 249 (32605056 bytes, f MiB)
> Amount of available logical eraseblocks: 112 (14665728 bytes, f MiB)
> Maximum count of volumes 128
> Count of bad physical eraseblocks: 0
> Count of reserved physical eraseblocks: 0
> Current maximum erase counter value: 72
> Minimum input/output unit size: 1 byte
> Character device major/minor: 253:0
> Present volumes: 0, 1
>
> Volume ID: 0 (on ubi0)
> Type: static
> Alignment: 1
> Size: 27 LEBs (3535488 bytes, f MiB)
> Data bytes: 3481728 bytes (f MiB)
> State: OK
> Name: kernel
> Character device major/minor: 253:1
> -----------------------------------
> Volume ID: 1 (on ubi0)
> Type: static
> Alignment: 1
> Size: 106 LEBs (13880064 bytes, f MiB)
> Data bytes: 13844480 bytes (f MiB)
> State: OK
> Name: squashfs
> Character device major/minor: 253:2
> (initramfs)
> (initramfs) ubimkvol -m -N ubifs /dev/ubi0
> Set volume size to 14665728
> Volume ID 2, size 112 LEBs (14665728 bytes, f MiB), LEB size 130944
> bytes (f KiB), dynamic, name "ubifs", alignment 1
> (initramfs)
> (initramfs) mkdir /mnt
> (initramfs) mount -t ubifs ubi0:ubifs /mnt
> [ 277.900000] UBIFS: default file-system created
> [ 277.980000] UBIFS DBG (pid 1497): ubifs_bg_thread: background
> thread "ubifs_bgt0_2" started, PID 1497
> [ 278.260000] UBIFS error (pid 1493): check_lpt_crc: invalid crc in
> LPT node: crc cbcb calc cbfb
> [ 278.260000] [<c01822bc>] (unwind_backtrace+0x0/0x160) from
> [<bf071a34>] (check_lpt_crc+0x9c/0xb0 [ubifs])
> [ 278.270000] [<bf071a34>] (check_lpt_crc+0x9c/0xb0 [ubifs]) from
> [<bf071b24>] (unpack_pnode+0xdc/0xfc [ubifs])
> [ 278.280000] [<bf071b24>] (unpack_pnode+0xdc/0xfc [ubifs]) from
> [<bf071d8c>] (scan_get_pnode+0x248/0x2ec [ubifs])
> [ 278.300000] [<bf071d8c>] (scan_get_pnode+0x248/0x2ec [ubifs]) from
> [<bf072738>] (ubifs_lpt_scan_nolock+0x3f8/0x518 [ubifs])
> [ 278.310000] [<bf072738>] (ubifs_lpt_scan_nolock+0x3f8/0x518
> [ubifs]) from [<bf0754b8>] (dbg_check_lprops+0xf8/0x2e4 [ubifs])
> [ 278.320000] [<bf0754b8>] (dbg_check_lprops+0xf8/0x2e4 [ubifs]) from
> [<bf051ff4>] (mount_ubifs+0x6a4/0x1620 [ubifs])
> [ 278.330000] [<bf051ff4>] (mount_ubifs+0x6a4/0x1620 [ubifs]) from
> [<bf053d20>] (ubifs_fill_super+0x318/0x42c [ubifs])
> [ 278.340000] [<bf053d20>] (ubifs_fill_super+0x318/0x42c [ubifs])
> from [<bf053f0c>] (ubifs_get_sb+0xd8/0x22c [ubifs])
> [ 278.350000] [<bf053f0c>] (ubifs_get_sb+0xd8/0x22c [ubifs]) from
> [<c01f5360>] (vfs_kern_mount+0x68/0x12c)
> [ 278.360000] [<c01f5360>] (vfs_kern_mount+0x68/0x12c) from
> [<c01f5468>] (do_kern_mount+0x34/0xdc)
> [ 278.370000] [<c01f5468>] (do_kern_mount+0x34/0xdc) from
> [<c020dad0>] (do_mount+0x210/0x244)
> [ 278.380000] [<c020dad0>] (do_mount+0x210/0x244) from [<c020dba0>]
> (sys_mount+0x9c/0xd0)
> [ 278.390000] [<c020dba0>] (sys_mount+0x9c/0xd0) from [<c017c9e0>]
> (ret_fast_syscall+0x0/0x2c)
> [ 278.400000] UBIFS DBG (pid 1497): ubifs_bg_thread: background
> thread "ubifs_bgt0_2" stops
> mount: Invalid argument
Do you see this problem with mtdram, which emulates NOR in RAM? The
problem is very strange. See modinfo mtdram for its parameters.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-01-12 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 18:56 Fail to mount ubifs Jon Ringle
2010-01-12 0:20 ` Jon Ringle
2010-01-12 4:50 ` Artem Bityutskiy
2010-01-12 12:07 ` Jon Ringle
2010-01-12 21:37 ` Artem Bityutskiy
2010-01-13 0:40 ` Jon Ringle
2010-01-12 20:23 ` Jon Ringle
2010-01-12 20:49 ` Jon Ringle
2010-01-12 21:23 ` Jon Ringle
2010-01-12 21:38 ` Artem Bityutskiy
2010-01-12 21:30 ` Artem Bityutskiy
2010-01-13 0:15 ` Jon Ringle
2010-01-13 7:03 ` Jon Ringle
2010-01-13 7:55 ` Artem Bityutskiy
2010-01-13 8:06 ` Artem Bityutskiy
2010-01-13 14:20 ` Jon Ringle
2010-01-12 21:33 ` Artem Bityutskiy [this message]
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=1263331986.3445.7.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=jon@ringle.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.