From: Richard Weinberger <richard.weinberger@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>,
Jonas Holmberg <jonashg@axis.com>,
Cristian Ionescu-Idbohrn <cii@axis.com>
Subject: Re: Actual usage of files in ubifs
Date: Mon, 11 Sep 2017 16:55:05 +0200 [thread overview]
Message-ID: <CAFLxGvz+_m0u6naPErkYMH2o53muj5TxNVSH82uKF-_FX9SesA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1709111143420.14549@lnxricardw1.se.axis.com>
On Mon, Sep 11, 2017 at 11:47 AM, Ricard Wanderlof
<ricard.wanderlof@axis.com> wrote:
>
> Is there a (simple) way to find out exactly how much space each specific
> file uses in an ubifs fils system?
>
> I looked into running mkfs.ubifs with some form of option to give me the
> info, the closest I got was -g 3 which output a lot of sizes but it was
> not obvious exactly what they meant.
>
> I suppose it would be fully possible to add code to mkfs.ubifs to output
> this information, as it surely must be there at some point, since it
> selects the compression algorithm on a file per file basis, debending on
> the amount of compression acheived for each algorithm.
Well, how exactly should it be?
I guess you want more than the compressed size on flash.
Do you also want to know how much bytes a file occupies in the index
tree and the inode itself?
This is non-trivial.
--
Thanks,
//richard
next prev parent reply other threads:[~2017-09-11 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 9:47 Actual usage of files in ubifs Ricard Wanderlof
2017-09-11 14:55 ` Richard Weinberger [this message]
2017-09-11 15:18 ` Ricard Wanderlof
2017-09-11 15:44 ` Artem Bityutskiy
2017-09-11 19:57 ` Richard Weinberger
2017-09-12 9:15 ` Ricard Wanderlof
2017-09-12 14:52 ` Richard Weinberger
2017-09-15 22:08 ` Ricard Wanderlof
2017-09-16 6:32 ` Richard Weinberger
2017-09-18 6:37 ` Ricard Wanderlof
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=CAFLxGvz+_m0u6naPErkYMH2o53muj5TxNVSH82uKF-_FX9SesA@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=cii@axis.com \
--cc=jonashg@axis.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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.