From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stefani Seibold <stefani@seibold.net>
Cc: "Kreuzer, Michael \(NSN - DE/Ulm\)" <michael.kreuzer@nsn.com>,
linux-mtd@lists.infradead.org, "Pagliari,
Vivenzio \(NSN - DE/Ulm\)" <vivenzio.pagliari@nsn.com>,
"Matthew L. Creech" <mlcreech@gmail.com>
Subject: Re: ubi_eba_init_scan: cannot reserve enough PEBs
Date: Thu, 02 Sep 2010 12:45:18 +0300 [thread overview]
Message-ID: <1283420718.1748.3.camel@brekeke> (raw)
In-Reply-To: <1283410033.6920.30.camel@wall-e.seibold.net>
On Thu, 2010-09-02 at 08:47 +0200, Stefani Seibold wrote:
>
> That is the point! Panic or refuse to mount is not a good solution. If
> there is a way to mount the file system, than do it. Maybe read-only
> with a big fat warning, but this is better than nothing. This is like
> the ext3 fs, which handles this also in this way.
>
> > In your case you have very strange corruption. We can apply your
> patch,
> > problem solved, but will you be 100% comfortable with this? There is
> a
> > chance that you have some issues which can later have different
> > symptoms. I am still interested to find out the real root reason.
> >
>
> No a will be not 100% comfortable with this, but it is better than
> nothing. I agree with you to fix the cause and not the symptoms, but
> may
> patch will help to get your data back in case of this bug.
May be. I need some more time to think about this.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-09-02 9:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 18:37 ubi_eba_init_scan: cannot reserve enough PEBs Matthew L. Creech
2010-07-26 5:21 ` Artem Bityutskiy
2010-07-26 21:13 ` Matthew L. Creech
2010-07-27 15:12 ` Artem Bityutskiy
2010-07-27 15:21 ` Artem Bityutskiy
2010-07-28 5:46 ` Stefani Seibold
2010-08-22 15:04 ` Artem Bityutskiy
2010-08-31 12:09 ` Stefani Seibold
2010-09-01 15:47 ` Artem Bityutskiy
2010-09-02 6:47 ` Stefani Seibold
2010-09-02 9:45 ` Artem Bityutskiy [this message]
2010-08-22 15:02 ` Artem Bityutskiy
2010-07-27 20:47 ` Matthew L. Creech
2010-07-30 16:12 ` Artem Bityutskiy
2010-07-30 17:51 ` Matthew L. Creech
2010-08-02 4:22 ` Artem Bityutskiy
2010-08-22 18:30 ` Artem Bityutskiy
2010-08-24 22:38 ` Matthew L. Creech
2010-08-25 3:51 ` Artem Bityutskiy
2010-08-31 15:36 ` Matthew L. Creech
2010-09-01 18:57 ` Artem Bityutskiy
2010-09-06 9:17 ` Artem Bityutskiy
2010-09-07 15:59 ` Matthew L. Creech
2010-09-07 17:17 ` Artem Bityutskiy
2010-09-07 17:48 ` Artem Bityutskiy
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=1283420718.1748.3.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.kreuzer@nsn.com \
--cc=mlcreech@gmail.com \
--cc=stefani@seibold.net \
--cc=vivenzio.pagliari@nsn.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.