From: Richard Weinberger <richard@nod.at>
To: Christoph Mammitzsch <Christoph.Mammitzsch@symeo.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Disappearing directories (jffs2 on nand flash)
Date: Tue, 05 Aug 2014 22:21:38 +0200 [thread overview]
Message-ID: <53E13CD2.6010000@nod.at> (raw)
In-Reply-To: <53E0A239.8060209@symeo.com>
Am 05.08.2014 11:22, schrieb Christoph Mammitzsch:
> Am 03.08.2014 01:13, schrieb Richard Weinberger:
>> On Sat, Aug 2, 2014 at 9:21 PM, Christoph Mammitzsch
>> <Christoph.Mammitzsch@symeo.com> wrote:
>>> Hello,
>>>
>>> I am a little astonished at the amount of feedback I got for my
>>> bugreport. Apparently jffs2 losing entire directories is not as big a
>>> deal as I thought. Does that mean that JFFS2 is dead and I should use
>>> another flash filesystem instead, or did I simply post on the wrong
>>> mailing list?
>>
>> Is there any reason why you are not using UBIFS?
>
> We introduced our first linux based product 2006, so UBIFS was not an
> option. Our second linux based product was designed in 2011. Back then
> UBIFS was still relatively new, and it seemed beneficial to keep
> differences between our two products minimal, so we kept using JFFS2.
>
> Switching to UBIFS now means we would have to update and test quite a
> lot of scripts. And providing an update for existing stations would be
> even more problematic. Therefore I was hoping for a bugfix, so we could
> just deliver a new kernel image and be done with it.
I can understand your decisions.
TBH jffs2 is more of less abandoned, don't expect anyone to fix issues fast.
Is the issue you see a regression?
If you can find the first bad commit it might give someone a hint...
git bisect will help you.
Thanks,
//richard
prev parent reply other threads:[~2014-08-05 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 17:00 Disappearing directories Christoph Mammitzsch
2014-07-15 17:23 ` Disappearing directories (jffs2 on nand flash) Christoph Mammitzsch
2014-08-02 19:21 ` Christoph Mammitzsch
2014-08-02 23:13 ` Richard Weinberger
2014-08-05 9:22 ` Christoph Mammitzsch
2014-08-05 20:21 ` 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=53E13CD2.6010000@nod.at \
--to=richard@nod.at \
--cc=Christoph.Mammitzsch@symeo.com \
--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;
as well as URLs for NNTP newsgroup(s).