From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matteo Mattei <matteo.mattei@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS mount error: No space left on device
Date: Sat, 28 Apr 2012 14:48:14 +0300 [thread overview]
Message-ID: <1335613694.1937.6.camel@koala> (raw)
In-Reply-To: <CAHea38QAtH52kLu29dztxLhfBBdPFdpSPUV3pyUxMCruBpPweg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
On Mon, 2012-04-23 at 14:34 +0200, Matteo Mattei wrote:
> Hi guys,
>
> After about 2 weeks with continuous read/write stress operation (w/o
> powercycles) I moved a board to the power-cycles reliability lab to
> perform also some other tests.
> After a while I had an error during mounting the filesystem.
>
> After a further analysis seems that there is not enough space to mount
> the device (I don't know who is the responsible for this because there
> is a quite big empty space in the device).
Yeah, I fixed several issues with this symptom in the past, probably not
all of them.
> Can you clarify why this strange behavior happened?
Probably a bug.
> Maybe there is not enough space in the journal?!
May be. I'd need your image to take a look - did you save it?
> Is there a way to avoid this or a workaround to let me to recover the board?
Well, you can re-size the UBI volume a bit and add a couple more LEBs to
work this around.
> I have also one other question but not strictly related to this issue
> (maybe there are already some other threads on this, but I didn't find
> the answer): Do the UBI and UBIFS handle the erased space?
> If so, how do they handle it?
I do not understand the question.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-04-28 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:34 UBIFS mount error: No space left on device Matteo Mattei
2012-04-28 11:48 ` Artem Bityutskiy [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=1335613694.1937.6.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matteo.mattei@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.