public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Martin Townsend <mtownsend1973@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS assert when rebooting a read only ubifs when it's been remounted r/w
Date: Wed, 18 May 2016 12:13:07 +0200	[thread overview]
Message-ID: <573C4033.6010906@nod.at> (raw)
In-Reply-To: <CABatt_wMSQd7Tc=gP0rO53UghqjdaTonFFj4R_qu8zFJyfyz3A@mail.gmail.com>

Am 18.05.2016 um 11:24 schrieb Martin Townsend:
> A bit info:
> I booted the board over the network using TFTP/NFS and then mounting
> the UBIFS partition using
> ubiattach /dev/ubi_ctrl -m 12 -O 2048
> mount -o ro -t ubifs /dev/ubi0_0 /mnt/ubifs/
> but this never triggered the assert. So I thought maybe it was
> something to do with U-Boot mounting the rootfs to load the kernel and
> device tree which are in the UBIFS so I loaded the kernel and device
> tree from a TFTP server and then booted from NAND but this still
> triggered the assert so this kind of rules out U-Boot.

So, you can trigger without U-Boot touching the UBIFS?
Also no UBI attach happens in U-Boot?

Is the assert you're facing really the top most error?
Another question, goes the error way when you call "sync"
before remounting ro?

Thanks,
//richard

  parent reply	other threads:[~2016-05-18 10:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 15:19 UBIFS assert when rebooting a read only ubifs when it's been remounted r/w Martin Townsend
2016-05-17 16:13 ` Richard Weinberger
2016-05-18  9:24   ` Martin Townsend
2016-05-18  9:30     ` Martin Townsend
2016-05-18 10:13     ` Richard Weinberger [this message]
2016-05-18 10:39       ` Martin Townsend
2016-05-20  7:49         ` Richard Weinberger
2016-05-20  7:51           ` Richard Weinberger
2016-05-20  9:47           ` Martin Townsend
2016-05-23 14:16             ` Martin Townsend
2016-05-23 19:57               ` Richard Weinberger
2016-05-24  8:31                 ` Martin Townsend
2016-05-24  9:04                   ` Richard Weinberger
2016-05-24 10:37                     ` Martin Townsend
2016-05-24 12:26                       ` Richard Weinberger
2016-05-24 13:23                         ` Martin Townsend
2016-05-24 13:42                           ` Richard Weinberger
2016-05-24 14:12                             ` Martin Townsend
2016-05-24 16:51                               ` Richard Weinberger
2016-05-25  8:04                                 ` Martin Townsend
2016-10-12 13:07                                   ` Martin Townsend

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=573C4033.6010906@nod.at \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mtownsend1973@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox