From: Eric Sandeen <sandeen@redhat.com>
To: Bernhard Rohrer <graylion@sm-wg.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 blocksize peculiarities
Date: Fri, 24 Sep 2010 23:57:53 -0500 [thread overview]
Message-ID: <4C9D8151.7090800@redhat.com> (raw)
In-Reply-To: <4C9D640E.5020609@sm-wg.net>
Bernhard Rohrer wrote:
> Hi all
>
> I have a 3.3 TB partition (yes really) that is formatted with ext4 and 4
> kiB blocks. What little data I have on that appears to use up an
> extraordinary amount of space, so I had a closer look.
>
> root@newcollab:/home/adminlion# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/primary_vg-primary_var
> 3.5T 43G 3.3T 2% /var
>
> we see that 43 GiB appear to be taking up something that gets rounded to
> 200 GiB
by default 5% is reserved for the super-user, 5% of 3.3T is 168G,
168G + 43G is roughly 200G
-Eric
> if we look at:
>
> root@newcollab:/home/adminlion# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/mapper/primary_vg-primary_var
> 3696706360 44362800 3464561624 2% /var
>
> now 44362800 4k blocks are 169.23 GiB,
those are 1k blocks :)
Anyway, what you are seeing is the 5% reserved space, which does
not show up in "Used" but is reflected in "Avail"
It is confusing and you're not the first one to get tripped up :)
-Eric
> which does indeed round to 200
> GiB. similar usage also gets reported when I get the properties of the
> share via cifs.
>
> debugfs shows:
>
> Block count: 937689088
> Reserved block count: 46884454
> Free blocks: 912175341
>
> so while df shows 4 times as many available 1k blocks as debugfs, which
> after all shows the actual number of 4k blocks, both are more or less in
> agreement as to the space used. This leads me to believe that somehow
> only 1k of every 4k block gets used. Now i could of course reformat to
> 1k blocks, but I'd prefer to avoid that.
>
> OS is Lucid64 and the volume is a LVM volume.
>
> Has anybody seen this before? Uncle Google was rather mum on the subject.
>
> cheers
>
> Bernhard
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-09-25 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 2:53 ext4 blocksize peculiarities Bernhard Rohrer
2010-09-25 4:57 ` Eric Sandeen [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=4C9D8151.7090800@redhat.com \
--to=sandeen@redhat.com \
--cc=graylion@sm-wg.net \
--cc=linux-ext4@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 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.