From: Chris Jones <chrisjones@spin.net.au>
To: linux-kernel@vger.kernel.org
Cc: Roland Eggner <edvx1@systemanalysen.net>
Subject: Re: Linux source tree size difference issue
Date: Sat, 18 May 2013 12:00:01 +1000 [thread overview]
Message-ID: <5196E0A1.6000300@spin.net.au> (raw)
In-Reply-To: <20130517194419.GA4002@mobil.systemanalysen.net>
On 05/18/2013 05:44 AM, Roland Eggner wrote:
>
> $ LC_ALL=C du --help | grep -E -e 'apparent|sparse|fragmentation'
> -------------------------------------------------------------------
> --apparent-size print apparent sizes, rather than disk usage; although
> the apparent size is usually smaller, it may be
> larger due to holes in ('sparse') files, internal
> fragmentation, indirect blocks, and the like
> -b, --bytes equivalent to '--apparent-size --block-size=1'
>
Thanks Roland. I figured it out in the end. Things were not as bad as
they first seemed.
Regards
--
Chris Jones
Founder and Lead Software Architect
Paradise Software
chrisjones@spin.net.au
prev parent reply other threads:[~2013-05-18 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 0:20 Linux source tree size difference issue Chris Jones
2013-05-17 19:44 ` Roland Eggner
2013-05-18 2:00 ` Chris Jones [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=5196E0A1.6000300@spin.net.au \
--to=chrisjones@spin.net.au \
--cc=edvx1@systemanalysen.net \
--cc=linux-kernel@vger.kernel.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