All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Charles Godson <cestgodson@gmail.com>
Cc: Daniel Ehrenberg <dehrenberg@google.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Willy Tarreau <w@1wt.eu>
Subject: Re: Block device emulation on top of ubi volumes with read/write support
Date: Thu, 21 Jan 2016 10:29:03 +0100	[thread overview]
Message-ID: <56A0A4DF.3020504@nod.at> (raw)
In-Reply-To: <CADC-h+HHENRPJi=W4DyOMrmbPeCqu34Jsgux+X7jbHA+B51e_g@mail.gmail.com>

Am 21.01.2016 um 01:51 schrieb Charles Godson:
> On Wed, Jan 20, 2016 at 4:35 PM, Richard Weinberger <richard@nod.at> wrote:
>>
>> What is your fear?
>> If your NAND is loosing random blocks you are in trouble anyways.
>>
>> Thanks,
>> //richard
> More along the lines of having software blow away first 2K (or
> similar) of my mtd partition (sw bug). I think I would lose everything
> in that case, right? When I have multiple mtd partitions, I would lose
> only one of my file systems. However, all of this probably comes down
> to having backup images, if high availability and reliability is
> required.

If your software kills random blocks you're better with multiple
partitions due to backups...But as the kernel is software too... ;)

Strictly speaking you'd not lose everything after say 2k are gone.
But have to recover the data manually. :)

Thanks,
//richard

      reply	other threads:[~2016-01-21  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADC-h+GSekez10TVYV3pJsiD=YPY=WawG5cN_ZrJJb0zP7Xu=g@mail.gmail.com>
2016-01-20 21:50 ` Block device emulation on top of ubi volumes with read/write support Ezequiel Garcia
2016-01-20 22:39   ` Richard Weinberger
     [not found]     ` <CADC-h+H=qwue4Ubr7kKOxjweH_0npTwepvnemcnEKAtb3sMPcA@mail.gmail.com>
2016-01-20 23:54       ` Daniel Ehrenberg
2016-01-21  0:12         ` Richard Weinberger
2016-01-21  0:19           ` Daniel Ehrenberg
2016-01-21  0:21             ` Richard Weinberger
2016-01-21  0:29               ` Charles Godson
2016-01-21  0:35                 ` Richard Weinberger
2016-01-21  0:51                   ` Charles Godson
2016-01-21  9:29                     ` 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=56A0A4DF.3020504@nod.at \
    --to=richard@nod.at \
    --cc=cestgodson@gmail.com \
    --cc=dehrenberg@google.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-mtd@lists.infradead.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=w@1wt.eu \
    /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.