From: Stefani Seibold <stefani@seibold.net>
To: dedekind1@gmail.com
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: Tue, 31 Aug 2010 14:09:47 +0200 [thread overview]
Message-ID: <1283256587.7515.16.camel@wall-e.seibold.net> (raw)
In-Reply-To: <1282489456.16502.74.camel@brekeke>
Am Sonntag, den 22.08.2010, 18:04 +0300 schrieb Artem Bityutskiy:
>
> Yes, but your patch fixes the symptom, unfortunately. It is ok for you
> to use as a work-around, but I still hope to find the root cause.
>
True, but also if we fix the cause, this could happen. Imagine that one
of the two master LEB will get corrupted, due a flash error or a power
fail during a write access. Than the system should able to mount this
damaged file system and restore the lost master LEB.
We should try to make UBIFS as robustly as possible and handle all
possible errors.
My path is only a first idea to solve this kind of problem. I think it
must enhanced by restoring the LEB when the filesystem is mounted
read-write.
I think it is important to be a bit more defensive and assume the worst
case.
- Stefani
next prev parent reply other threads:[~2010-08-31 12:09 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 [this message]
2010-09-01 15:47 ` Artem Bityutskiy
2010-09-02 6:47 ` Stefani Seibold
2010-09-02 9:45 ` Artem Bityutskiy
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=1283256587.7515.16.camel@wall-e.seibold.net \
--to=stefani@seibold.net \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.kreuzer@nsn.com \
--cc=mlcreech@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).