Linux-mtd Archive on lore.kernel.org
 help / color / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Ben Schroeder <klowd92@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Available space loss due to fragmentation?
Date: Thu, 11 Jul 2019 22:41:56 +0200 (CEST)
Message-ID: <978087654.37118.1562877716708.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAMk-x8PdwHryEmot4drePgx9cRfL6mO2FoURm5HSWdJjN97yhQ@mail.gmail.com>

Ben,

----- Ursprüngliche Mail -----
> Von: "Ben Schroeder" <klowd92@gmail.com>
> An: "Richard Weinberger" <richard.weinberger@gmail.com>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> Gesendet: Donnerstag, 11. Juli 2019 17:53:53
> Betreff: Re: Available space loss due to fragmentation?

> On Thu, Jul 11, 2019 at 1:16 PM Richard Weinberger
> <richard.weinberger@gmail.com> wrote:
>>
>> On Wed, Jul 10, 2019 at 5:18 PM Ben Schroeder <klowd92@gmail.com> wrote:
>> > Thanks for the reply Richard.
>> > I just wanted to reiterate that i am using SPI NOR Flash, partitioned
>> > in an A/B scheme as so:
>>
>> Hmmm.
>> Did you create the rootfs using mkfs.ubifs with a different
>> compression than used
>> by the kernel?
> mkfs.ubifs -r /tmp/rootfs -m 1 -e 0xFF80 -c 1024 -o data.ubifs
> (I believe standard compression is used, lzo?)

To be honest, I'm not entirely sure what problem you are facing.

Can you please give these two approaches a try?
1. Create the filesystem with no compression and mount ubifs without compression,
to rule out compression related issues.
2. Try a (much) larger log size, you can specify it at mkfs.ubifs time.

Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  3:32 Ben Schroeder
2019-07-10  9:34 ` Richard Weinberger
2019-07-10 15:18   ` Ben Schroeder
2019-07-11 10:16     ` Richard Weinberger
2019-07-11 15:53       ` Ben Schroeder
2019-07-11 20:41         ` Richard Weinberger [this message]

Reply instructions:

You may reply publically 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=978087654.37118.1562877716708.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=klowd92@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@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

Linux-mtd Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-mtd/0 linux-mtd/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-mtd linux-mtd/ https://lore.kernel.org/linux-mtd \
		linux-mtd@lists.infradead.org linux-mtd@archiver.kernel.org
	public-inbox-index linux-mtd


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-mtd


AGPL code for this site: git clone https://public-inbox.org/ public-inbox