mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland Eggner <edvx1@systemanalysen.net>
To: Chris Jones <chrisjones@spin.net.au>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux source tree size difference issue
Date: Fri, 17 May 2013 21:44:19 +0200	[thread overview]
Message-ID: <20130517194419.GA4002@mobil.systemanalysen.net> (raw)
In-Reply-To: <519577DD.3040204@spin.net.au>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On 2013-05-17 Friday at 10:20 +1000 Chris Jones wrote:
> I have cloned the Linux kernel source tree locally. It comes in at
> approx. ~500MB. I have then created another git repository to push the
> source to for my own work. I rsynced the tree locally to another
> directory and now I am currently pushing it in to the new repository and
> it's at 58% and is already at 525MB.
> 
> I can not understand the stark difference in source and directory size.
> Running diff tells me both local source tree directories are exactly the
> same.
> 
> Can anyone explain this in layman's terms?

$  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'

-- 
Regards
Roland Eggner

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-05-17 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  0:20 Chris Jones
2013-05-17 19:44 ` Roland Eggner [this message]
2013-05-18  2:00   ` Chris Jones

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=20130517194419.GA4002@mobil.systemanalysen.net \
    --to=edvx1@systemanalysen.net \
    --cc=chrisjones@spin.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®