public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: read-only FS with error -2
Date: Sun, 28 Oct 2018 16:21:31 +0100	[thread overview]
Message-ID: <12453083.5lVtCAIVAB@blindfold> (raw)
In-Reply-To: <80fe0c51-d651-13ac-a985-a0ee6b5d7edd@candelatech.com>

Ben,

Am Sonntag, 28. Oktober 2018, 16:08:13 CET schrieb Ben Greear: 
> That is not an easy thing to do on random embedded systems.  Possibly I could add a kernel

Debugging random non-development systems is never easy.

> command line option...is that supported?

The UBIFS module takes no parameters. But patches are welcome.
For now you can just use your initramfs (AFAIK OpenWRT has one), boot with rdinit=/bin/sh ...

Or apply a hacky patch like this one to enable chk_fs always...

diff --git a/fs/ubifs/debug.h b/fs/ubifs/debug.h
index 64c6977c189b..ea0ffc0a9660 100644
--- a/fs/ubifs/debug.h
+++ b/fs/ubifs/debug.h
@@ -231,7 +231,7 @@ static inline int dbg_is_chk_lprops(const struct ubifs_info *c)
 }
 static inline int dbg_is_chk_fs(const struct ubifs_info *c)
 {
-	return !!(ubifs_dbg.chk_fs || c->dbg->chk_fs);
+	return 1;
 }
 static inline int dbg_is_tst_rcvry(const struct ubifs_info *c)
 {

Thanks,
//richard

  reply	other threads:[~2018-10-28 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 18:39 read-only FS with error -2 Ben Greear
2018-10-27 20:36 ` Richard Weinberger
2018-10-27 22:37   ` Ben Greear
2018-10-28 11:17     ` Richard Weinberger
2018-10-28 15:08       ` Ben Greear
2018-10-28 15:21         ` Richard Weinberger [this message]
2018-10-28 18:44           ` Ben Greear
2018-10-28 18:59             ` Richard Weinberger

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=12453083.5lVtCAIVAB@blindfold \
    --to=richard@nod.at \
    --cc=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox