All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Bruce_Leonard@selinc.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problem mounting a UBIFS volume
Date: Thu, 03 Jul 2008 09:11:35 +0300	[thread overview]
Message-ID: <1215065495.6573.106.camel@sauron> (raw)
In-Reply-To: <OF565C42CF.2A35DC45-ON8825747B.001B2100-8825747B.001D1F69@selinc.com>

Hi Bruce,

On Wed, 2008-07-02 at 22:18 -0700, Bruce_Leonard@selinc.com wrote:
> Artem,
> 
> I'm trying to wrap up my changes to support >8GiB MTD devices so it can be 
> tested while I'm on vacation.  For the most part things run okay (I think 
> :-\  ).  I can load UBI and UBIFS.  ubimkvol/ubirmvol seem to work okay 
> and I can mount/read/write/umount volumes created with ubimkvol.  But I 
> have a problem when using mkfs.ubifs and I'm not sure if the problme is in 
> mkfs.ubifs or in the kernel.  mkfs.ubifs runs fine and finishes without 
> complaining.  ubiupdatevol seems to have no problems writing the image to 
> the device.  When I try to mount the volume, though, it fails to mount and 
> gives the following error:

Did you use your MTD 64-bit patch? Did you create a large FS image with
mkfs.ubifs? How large is the ubifs image?

> UBIFS error (pid 824): ubifs_read_nnode: error -22 reading nnode at 8:6150
> UBIFS DBG (pid 825): ubifs_bg_thread: background thread "ubifs_bgt0_0" 
> stops
> 
> 
> Now obviously there's a CRC mismatch between what was written to the flash 
> and what UBIFS calculated.  At first I thought it might be an endian issue 
> (my system is an MPC8347E running the tip of the UBIFS tree and the latest 
> UBI tools and mkfs.ubifs), but I don't think so since the stored CRC is 
> clearly different from the calculated.  I'm digging trying to find the 
> problem but I'm into things I've never seen before and don't yet 
> understand.  I now suspect that it's probably another one of those 64-bit 
> promotions I've been fighting, but I'm not sure.  Any guidence you can 
> give would be appreciated.

We'll look at this, thanks for the report.

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

  reply	other threads:[~2008-07-03  6:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  5:18 Problem mounting a UBIFS volume Bruce_Leonard
2008-07-03  6:11 ` Artem Bityutskiy [this message]
2008-07-03  6:26   ` Bruce_Leonard
2008-07-03  6:38   ` Bruce_Leonard
2008-07-04 13:02 ` Artem Bityutskiy
2008-07-23 22:26   ` Bruce_Leonard
2008-07-24  6:18     ` Adrian Hunter
2008-07-28  9:16       ` Adrian Hunter
2008-08-12  4:58         ` Bruce_Leonard
2008-08-12  8:41           ` Adrian Hunter
2008-08-12 23:34             ` Bruce_Leonard

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=1215065495.6573.106.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=Bruce_Leonard@selinc.com \
    --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.