From: Artem Bityutskiy <dedekind@infradead.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: can't mount ubifs on volume smaller than 265 LEBs/32MiB
Date: Fri, 04 Apr 2008 09:48:57 +0300 [thread overview]
Message-ID: <1207291737.8040.24.camel@sauron> (raw)
In-Reply-To: <1207285579.8040.14.camel@sauron>
On Fri, 2008-04-04 at 08:06 +0300, Artem Bityutskiy wrote:
> I'll look at this shortly, thanks for the report. As a suggestion, if
> you have problems with UBIFS and going to send a bug-report, try to
> enable debugging, reproduce the problem and send dmesg. With debugging
> enabled it prints more useful information and makes it easier to
> identify and fix the issue.
Adrian said he fixed a validation bug recently, so you should update and
the problem will probably go away.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-04-04 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 4:12 can't mount ubifs on volume smaller than 265 LEBs/32MiB Hamish Moffatt
2008-04-04 5:06 ` Artem Bityutskiy
2008-04-04 6:48 ` Artem Bityutskiy [this message]
2008-04-07 1:31 ` Hamish Moffatt
2008-04-04 8:48 ` Artem Bityutskiy
2008-04-04 5:25 ` 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=1207291737.8040.24.camel@sauron \
--to=dedekind@infradead.org \
--cc=hamish@cloud.net.au \
--cc=linux-mtd@lists.infradead.org \
/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