All of lore.kernel.org
 help / color / mirror / Atom feed
From: JH <jupiter.hce@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Steve deRosier <derosier@gmail.com>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: How the bad blocks occured in despite MTD manages the bad blocks
Date: Sun, 6 Oct 2019 08:56:41 +1100	[thread overview]
Message-ID: <CAA=hcWS5ctErRzJXj0p5+-vVMzGc0U-JF27ZXkM-FMHZ=kz3Fg@mail.gmail.com> (raw)
In-Reply-To: <CAFLxGvyWTSgCQz-wdM9KBR4t45_pBBzWUJSW3j09HyBy+VAmbg@mail.gmail.com>

On 10/5/19, Richard Weinberger <richard.weinberger@gmail.com> wrote:
>> [    6.057136] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0),
>> UUID E9F1667C-8AC1-4030-BB1A-9C5341482A61, small LPT model
>> [    6.074491] VFS: Mounted root (ubifs filesystem) on device 0:13.
>
> So, UBIFS is happy and mounts cleanly.

Oh good, relieved.

>> [    8.732692] systemd[126]: sys-kernel-debug.mount: Failed to execute
>> command: No such file or directory
>> [    8.742715] systemd[128]: sys-fs-fuse-connections.mount: Failed to
>> execute command: No such file or directory
>
> Some files are missing but it does not look like a UBIFS corruption.
> In case of corruption (such as dead directory entry) UBIFS would cry out
> loud.
>
> I don't see a problem which points to the storage stack.

So if the UBIFS was not corrupted, NAND was not damaged, is my
assertion rational that software / kernel was not the cause to break
the system and device down?

Thank you very much Richard.

Kind regards,

- jh

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2019-10-05 21:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 10:35 How the bad blocks occured in despite MTD manages the bad blocks JH
2019-10-02 16:09 ` Steve deRosier
2019-10-02 16:13 ` Richard Weinberger
2019-10-03 11:14   ` JH
2019-10-03 13:28     ` Richard Weinberger
2019-10-03 21:26       ` JH
2019-10-03 23:44         ` Steve deRosier
2019-10-04  6:36           ` JH
2019-10-05  8:38             ` Richard Weinberger
2019-10-05 21:56               ` JH [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='CAA=hcWS5ctErRzJXj0p5+-vVMzGc0U-JF27ZXkM-FMHZ=kz3Fg@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --cc=derosier@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@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 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.