All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iwo Mergler <Iwo.Mergler@netcommwireless.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: RE: UBIFS fails to mount on second boot
Date: Wed, 18 Jul 2012 17:05:24 +1000	[thread overview]
Message-ID: <6871BC8982B258468985EE735D2C57524B09D0EECD@ntcex01.corp.netcomm.com.au> (raw)
In-Reply-To: <1342240778.3209.12.camel@brekeke>


Artem Bityutskiy <dedekind1@gmail.com> wrote:
> I suspect this is a bug in the free space fixup code - my level of
> confidence on this is 80%. Could you please verify this by removing
> the -F mkfs.ubifs parameter or using the patch below. Thanks!

You're right, the problem doesn't happen without fixup.

I thought I was not flashing empty pages in U-Boot, but that turned
out not to be quite true. Without fixup, the boot died in a hailstorm
of asserts. I fixed that, but now the flashing takes noticeably longer.

In other words, I quite like the fixup feature and would prefer if it doesn't
go away permanently. Otherwise:

Tested-by: Iwo Mergler <Iwo.Mergler@netcommwireless.com>

> 
> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
> index 5862dd9..3398114 100644
> --- a/fs/ubifs/super.c
> +++ b/fs/ubifs/super.c
> @@ -1295,11 +1295,13 @@ static int mount_ubifs(struct ubifs_info *c)
>  	if (err)
>  		goto out_master;
>  
> +#if 0
>  	if (!c->ro_mount && c->space_fixup) {
>  		err = ubifs_fixup_free_space(c);
>  		if (err)
>  			goto out_lpt;
>  	}
> +#endif
>  
>  	if (!c->ro_mount) {
>  		/*
> 

Best regards,

Iwo

______________________________________________________________________
This communication contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above.  If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited.  If you have received this communication in error, please notify me by telephone immediately.
______________________________________________________________________

  reply	other threads:[~2012-07-18  7:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  5:23 UBIFS fails to mount on second boot Iwo
2012-06-27 14:10 ` Artem Bityutskiy
2012-06-29  6:05   ` Iwo Mergler
2012-06-29 13:46     ` Artem Bityutskiy
2012-07-02  7:49       ` Iwo Mergler
2012-07-03  1:16         ` Iwo Mergler
2012-07-14  4:39           ` Artem Bityutskiy
2012-07-18  7:05             ` Iwo Mergler [this message]
2012-07-18  7:21               ` Artem Bityutskiy
2012-07-19  1:06                 ` Iwo Mergler
2012-07-15  8:25         ` 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=6871BC8982B258468985EE735D2C57524B09D0EECD@ntcex01.corp.netcomm.com.au \
    --to=iwo.mergler@netcommwireless.com \
    --cc=dedekind1@gmail.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.