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 19:59:52 +0100	[thread overview]
Message-ID: <3653061.hV2SDYrdd6@blindfold> (raw)
In-Reply-To: <0e90fe2a-1747-7a4c-9b6b-576dfdfad86d@candelatech.com>

Ben,

Am Sonntag, 28. Oktober 2018, 19:44:46 CET schrieb Ben Greear:
> > 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...
> 
> Problem is, when I re-install then the problem goes away.  Would it
> be bad to enable this code all the time on production systems?

Did you face the problem more than *once*?

chk_fs makes mounting very slow, it is basically a fsck upon mount.
 
> Could UBIFS just enable debugging and print out any pertinent
> info when it detects the failure instead of (just) going into RO
> mode?

UBIFS prints a ton on debug information upon unexpected situations.
But if your logs are gone and you have only very the last one (after a reboot),
UBIFS cannot do much...

Thanks,
//richard

      reply	other threads:[~2018-10-28 19:00 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
2018-10-28 18:44           ` Ben Greear
2018-10-28 18:59             ` Richard Weinberger [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=3653061.hV2SDYrdd6@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